Triple
T6542043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest–East Line |
E168311
|
entity |
| Predicate | transportSystemType |
P56025
|
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: [Northwest–East Line, transportSystemType, rapid transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportSystemType Context triple: [Northwest–East Line, transportSystemType, rapid transit]
-
A.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
B.
typeOfTransportInfrastructure
chosen
Indicates the specific category or kind of transport infrastructure associated with or used in a given context.
-
C.
hasTransportationSystem
Indicates that an entity possesses, operates, or is served by an organized system for transporting people or goods.
-
D.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
E.
transports
Indicates that one entity carries or conveys another entity from one place to another.
- 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_69c68a51564081909e93aee0dbd9cca3 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:50 p.m.