Triple
T7788404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amaravati |
E187306
|
entity |
| Predicate | distanceToGuntur |
P79015
|
FINISHED |
| Object | approximately 30 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 30 km | Statement: [Amaravati, distanceToGuntur, approximately 30 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGuntur Context triple: [Amaravati, distanceToGuntur, approximately 30 km]
-
A.
distanceToHyderabad
Indicates the spatial distance between a given entity’s location and the city of Hyderabad.
-
B.
distanceFromGuwahati_km
Indicates the physical distance, measured in kilometers, between an entity and the location of Guwahati.
-
C.
distanceFromBangalore
Indicates the spatial distance separating a given entity or location from Bangalore.
-
D.
distanceFromBengaluru
Indicates the measured spatial distance between a given entity’s location and the city of Bengaluru.
-
E.
distanceFromTirupati
Indicates the measured distance between a given location and Tirupati.
- 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_69ca82af2d2c8190963861f5e0b8bf21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cae7e8a0d08190b6d4ca560681eb35 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
| PDg | Predicate description generation | batch_69cae7e47c5c8190bca90d45b3cdc25e |
completed | March 30, 2026, 9:15 p.m. |
Created at: March 30, 2026, 4:24 p.m.