Triple
T26453666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chakradharpur |
E665422
|
entity |
| Predicate | hasRailwayFacilities |
P19495
|
FINISHED |
| Object | loco shed |
—
|
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: loco shed | Statement: [Chakradharpur, hasRailwayFacilities, loco shed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailwayFacilities Context triple: [Chakradharpur, hasRailwayFacilities, loco shed]
-
A.
hasRailFacility
chosen
Indicates that an entity possesses or is served by a rail-related facility, such as a railway station, terminal, or yard.
-
B.
hasRailwayInfrastructureType
Indicates that an entity possesses or is associated with a specific type or category of railway infrastructure.
-
C.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
D.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
E.
hasRailOrRoadAccess
Indicates that an entity is connected to or reachable by either a railway network, a road network, or both.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 12:07 a.m.