Triple
T23520657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xi'an Rail Transit Group Co., Ltd. |
E574496
|
entity |
| Predicate | typeOfTransportProvided |
P1379
|
FINISHED |
| Object | rapid transit |
—
|
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: rapid transit | Statement: [Xi'an Rail Transit Group Co., Ltd., typeOfTransportProvided, rapid transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTransportProvided Context triple: [Xi'an Rail Transit Group Co., Ltd., typeOfTransportProvided, rapid transit]
-
A.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
B.
isTransportationType
Indicates that one entity functions as a mode or category of transportation for the other entity.
-
C.
transportAssumption
Indicates an assumption that something can be transported or carried from one place or context to another.
-
D.
transportModePresent
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
E.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa85cb2c81908afbd0df0caeef4d |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:08 p.m.