Triple
T35335947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phaphund |
E1020451
|
entity |
| Predicate | locatedOnRailwayZone |
P24188
|
FINISHED |
| Object | North Central Railway |
E546923
|
NE 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: North Central Railway | Statement: [Phaphund, locatedOnRailwayZone, North Central Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnRailwayZone Context triple: [Phaphund, locatedOnRailwayZone, North Central Railway]
-
A.
hasRailwayZone
chosen
Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
-
B.
isOnRailway
Indicates that one entity is positioned on, aligned with, or traveling along a railway track or railway system in relation to another entity.
-
C.
locatedOnFormerRailway
Indicates that something is situated on the route or site of a railway line that is no longer in operation.
-
D.
railwayZoneType
Indicates the classification or category of a railway zone to which a given railway-related entity belongs.
-
E.
railwayZoneNumber
Indicates the specific numbered zone of a railway network within which the referenced entity is located or classified.
- F. None of above.
Provenance (4 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3823cad1a08190a38ddc6ddec27fad |
completed | June 21, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.