Triple
T29693822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCH |
E751284
|
entity |
| Predicate | appliesToStationFunction |
P74029
|
FINISHED |
| Object | interchange station |
—
|
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: interchange station | Statement: [MCH, appliesToStationFunction, interchange station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToStationFunction Context triple: [MCH, appliesToStationFunction, interchange station]
-
A.
hasStationFunction
chosen
Indicates that an entity serves in a particular functional role or capacity at a station.
-
B.
appliesToTransitStation
Indicates that something (such as a rule, feature, condition, or attribute) is specifically relevant or applicable to a transit station.
-
C.
isStationOf
Indicates that a given location functions as a station (e.g., transport or service hub) associated with or serving a particular system, line, route, or organization.
-
D.
developedForStation
Indicates that something was specifically created or engineered to be used at or in connection with a particular station.
-
E.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: April 28, 2026, 7:18 p.m.