Triple
T22299126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shirdi |
E551205
|
entity |
| Predicate | distanceFromAhmednagar |
P147971
|
FINISHED |
| Object | approximately 80 km |
—
|
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: approximately 80 km | Statement: [Shirdi, distanceFromAhmednagar, approximately 80 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromAhmednagar Context triple: [Shirdi, distanceFromAhmednagar, approximately 80 km]
-
A.
distanceToNagpur
Indicates the spatial distance between a given entity’s location and the city of Nagpur.
-
B.
distanceFromNashik
Indicates the spatial distance between a given entity or location and the city of Nashik.
-
C.
distanceFromPune
Indicates the spatial distance between a given location or entity and the city of Pune.
-
D.
distanceFromAurangabad
Indicates the measured spatial distance between a given location and Aurangabad.
-
E.
distanceToAhmedabad
Indicates the spatial distance between a given location or entity and the city of Ahmedabad.
- F. None of above. chosen
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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15722c3348190b63eb49764ef132d |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e75dc7b08081909d64441e979c2fa4 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 16, 2026, 8:41 p.m.