Triple
T36536002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raipur railway division |
E900584
|
entity |
| Predicate | freightSpecialization |
P93658
|
FINISHED |
| Object | iron ore transport |
—
|
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: iron ore transport | Statement: [Raipur railway division, freightSpecialization, iron ore transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freightSpecialization Context triple: [Raipur railway division, freightSpecialization, iron ore transport]
-
A.
freightType
Indicates the category or mode of freight associated with a shipment or transport activity.
-
B.
freightConnections
Indicates the existence or characteristics of transportation links used to move freight or cargo between locations or entities.
-
C.
typeOfHaulage
Indicates the kind or category of haulage service or transport operation associated with an entity.
-
D.
cargoSpecialization
chosen
Indicates that an entity is specialized or designated for handling, transporting, or managing a particular type or category of cargo.
-
E.
logisticsFeature
Indicates that something possesses a characteristic, capability, or function specifically related to logistics operations or processes.
- 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.