Triple
T19900657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delhi–Chennai line |
E478275
|
entity |
| Predicate | usedByTrainType |
P56947
|
FINISHED |
| Object | superfast trains |
—
|
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: superfast trains | Statement: [Delhi–Chennai line, usedByTrainType, superfast trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByTrainType Context triple: [Delhi–Chennai line, usedByTrainType, superfast trains]
-
A.
trainTypeUsed
chosen
Indicates that a specific type or category of train is employed or operated in a given context or service.
-
B.
railServiceType
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
C.
railwayTypeServed
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.
-
D.
trainsCategory
Indicates that one entity is a category or type under which the other entity is trained or classified.
-
E.
usesRollingStockCompatibleWith
Indicates that one entity operates using rolling stock that is technically and operationally compatible with the rolling stock standards or systems associated with another entity.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65940cf8c8190b74e51635410e48a |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.