Triple
T23149615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jhansi–Gwalior–Agra section |
E578285
|
entity |
| Predicate | hasHistoricalCitiesOnRoute |
P65883
|
FINISHED |
| Object | Jhansi |
—
|
NE NERFINISHED |
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: Jhansi | Statement: [Jhansi–Gwalior–Agra section, hasHistoricalCitiesOnRoute, Jhansi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalCitiesOnRoute Context triple: [Jhansi–Gwalior–Agra section, hasHistoricalCitiesOnRoute, Jhansi]
-
A.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
-
B.
hasHistoricalRoute
Indicates that an entity possesses or is associated with a route that has historical significance or origin.
-
C.
historicalRouteVia
Indicates that a historical route or path passed through or was connected by a particular intermediate location or segment.
-
D.
passesHistoricCity
chosen
Indicates that a route, path, or entity travels through or goes by a city recognized for its historical significance.
-
E.
hasHistoricVillagesAlong
Indicates that a route, path, or geographic feature has historic villages located along its course or in close proximity to it.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ed0b76c8190ac61b949d88e9970 |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.