Triple
T18063369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airport East station |
E432233
|
entity |
| Predicate | roleOnLine1 |
P129674
|
FINISHED |
| Object | eastern terminus |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: eastern terminus | Statement: [Airport East station, roleOnLine1, eastern terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnLine1 Context triple: [Airport East station, roleOnLine1, eastern terminus]
-
A.
primaryRoleOnLine
Indicates that an entity serves as the main or most important role associated with a particular line (such as a transit line, product line, or communication line).
-
B.
ClientRole
Indicates that an entity participates in a relationship or interaction specifically in the capacity of a client.
-
C.
roleInFrame
Indicates that an entity participates in a specific semantic frame by filling a particular role within that frame.
-
D.
roleInProductLine
Indicates the specific functional or organizational role an entity holds within a particular product line.
-
E.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4cce5d2188190ba77d06061d6e77a |
completed | April 19, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:26 a.m.