Triple
T3263787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dongzhimen station |
E68474
|
entity |
| Predicate | lineRole_AirportExpress |
P33934
|
FINISHED |
| Object | 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: terminus | Statement: [Dongzhimen station, lineRole_AirportExpress, terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineRole_AirportExpress Context triple: [Dongzhimen station, lineRole_AirportExpress, terminus]
-
A.
airportLineRole
chosen
Indicates the specific functional role or responsibility an entity has in relation to an airport transit line or route.
-
B.
airportRole
Indicates that an entity serves a specific functional role or capacity within the context of an airport.
-
C.
connectsWithAirport
Indicates that there is a direct transportation or operational link established between an entity and an airport.
-
D.
railwayLineRole
Indicates the specific functional role or purpose that a railway line serves within a rail network or transportation system.
-
E.
railNetworkRole
Indicates the specific function or responsibility an entity has within a rail network system.
- F. None of above.
Provenance (3 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_69ad8590444081909e8107a8aeef3a23 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adafaa35e48190b894ca41dd65932b |
completed | March 8, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69ada41d7eac8190ada4bf5f793d5c49 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.