Triple
T4685519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhanushkodi Beach |
E103910
|
entity |
| Predicate | formerTransportLink |
P20480
|
FINISHED |
| Object | railway line to Dhanushkodi |
—
|
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: railway line to Dhanushkodi | Statement: [Dhanushkodi Beach, formerTransportLink, railway line to Dhanushkodi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerTransportLink Context triple: [Dhanushkodi Beach, formerTransportLink, railway line to Dhanushkodi]
-
A.
formerRailwayLine
chosen
Indicates that a railway line previously existed in the past but is no longer in operation or has been decommissioned.
-
B.
formerStationNameFor
Indicates that one station name was previously used as the official name for another station.
-
C.
isPublicTransportBackboneOf
Indicates that one transport system serves as the primary structural and functional core of a region’s overall public transportation network.
-
D.
operatorOfTransportInfrastructure
Indicates that an entity operates, manages, or runs a specific piece of transport infrastructure.
-
E.
partOfTransitSystem
Indicates that something is a component or segment within a larger transit or transportation system.
- 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.