Triple
T6564375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gonda |
E153864
|
entity |
| Predicate | distanceToLucknow_km |
P24190
|
FINISHED |
| Object | approximately 120 |
—
|
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 120 | Statement: [Gonda, distanceToLucknow_km, approximately 120]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLucknow_km Context triple: [Gonda, distanceToLucknow_km, approximately 120]
-
A.
distanceToLucknow
chosen
Indicates the spatial distance between a given entity’s location and the city of Lucknow.
-
B.
distanceFromPatna
Indicates the spatial distance between a given location and the city of Patna.
-
C.
distanceToDelhiByRail_km
Indicates the distance, measured in kilometers, from a given place to Delhi when traveling by rail.
-
D.
distanceToDelhiByRoad_km
Indicates the road travel distance, measured in kilometers, from a given place to Delhi.
-
E.
distanceToDelhiApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and Delhi.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:52 p.m.