Triple
T19966661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South East Central Railway zone |
E479952
|
entity |
| Predicate | majorCommodityTraffic |
P5941
|
FINISHED |
| Object | coal |
—
|
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: coal | Statement: [South East Central Railway zone, majorCommodityTraffic, coal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCommodityTraffic Context triple: [South East Central Railway zone, majorCommodityTraffic, coal]
-
A.
freightTraffic
Indicates the movement or volume of goods and cargo being transported, typically via commercial transport networks such as rail, road, sea, or air.
-
B.
majorTradeType
Indicates the primary category or kind of trade activity that characterizes the relationship between the involved entities.
-
C.
shipTraffic
Indicates the presence, movement, or volume of ships traveling through a particular waterway or maritime area.
-
D.
peakFreightTrafficRank
Indicates the relative ranking position of an entity based on the highest level of freight traffic it experiences or handles compared to others.
-
E.
mainCargo
chosen
Indicates that one entity serves as the primary or principal cargo carried or transported by 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc5e41881908c1e8867820f1c0c |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.