Triple
T14624581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koyambedu depot |
E343311
|
entity |
| Predicate | railSystemTypeServed |
P55099
|
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: [Koyambedu depot, railSystemTypeServed, rapid transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railSystemTypeServed Context triple: [Koyambedu depot, railSystemTypeServed, rapid transit]
-
A.
railwayTypeServed
chosen
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
-
B.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
C.
railServiceType
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
D.
hasRailSystem
Indicates that an entity possesses or is served by a rail-based transportation system.
-
E.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb468acc4819083b7e818d5cec809 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:26 a.m.