Triple
T18436521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambala railway division |
E450405
|
entity |
| Predicate | typeOfTrafficHandled |
P27465
|
FINISHED |
| Object | passenger traffic |
—
|
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: passenger traffic | Statement: [Ambala railway division, typeOfTrafficHandled, passenger traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTrafficHandled Context triple: [Ambala railway division, typeOfTrafficHandled, passenger traffic]
-
A.
cargoTrafficRank
Indicates the relative position of an entity in an ordered list based on the volume or intensity of its cargo traffic.
-
B.
trafficType
Indicates the category or nature of traffic involved in a given interaction, flow, or connection (e.g., type of network, data, or transport traffic).
-
C.
majorTrafficType
chosen
Indicates the primary kind of traffic or flow that predominantly characterizes a given route, segment, or transportation context.
-
D.
annualTraffic
Indicates the typical amount or volume of traffic associated with something over the course of a year.
-
E.
handlesCargoTraffic
Indicates that an entity is responsible for managing or processing the movement of cargo traffic.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c0cd30c8190b8417c264e60d3a5 |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:29 a.m.