Triple
T23800842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tikamgarh railway station |
E588666
|
entity |
| Predicate | hasExpressTrains |
P103546
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tikamgarh railway station, hasExpressTrains, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpressTrains Context triple: [Tikamgarh railway station, hasExpressTrains, yes]
-
A.
hasExpressTracks
Indicates that a transportation route or facility includes tracks designated for express service, allowing faster travel with fewer stops than regular tracks.
-
B.
hasLongDistanceTrains
chosen
Indicates that a location, station, or rail operator provides or is served by long-distance train services.
-
C.
hasHighSpeedLine
Indicates that there exists a high-speed rail line connection between the related entities.
-
D.
hasNightTrainService
Indicates that a transportation route or station is served by trains that operate during nighttime hours.
-
E.
hasRegionalTrainService
Indicates that a location or route is served by regional train services connecting it to nearby areas.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6e0814081908a81e1ede05ab810 |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:53 p.m.