Triple
T9051435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Management Authority for Urban Railways |
E216890
|
entity |
| Predicate | hasRailSystemType |
P18634
|
FINISHED |
| Object | metro |
—
|
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: metro | Statement: [Management Authority for Urban Railways, hasRailSystemType, metro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailSystemType Context triple: [Management Authority for Urban Railways, hasRailSystemType, metro]
-
A.
hasRailSystem
Indicates that an entity possesses or is served by a rail-based transportation system.
-
B.
railSystemType
chosen
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
C.
hasRailwayInfrastructureType
Indicates that an entity possesses or is associated with a specific type or category of railway infrastructure.
-
D.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
-
E.
hasRailMode
Indicates that an entity is associated with or supports transportation via rail-based modes (such as trains, trams, or subways).
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b54423081908d9fd985109e336a |
completed | April 1, 2026, 12:48 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:10 p.m.