Triple
T3434283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golconda Fort |
E72409
|
entity |
| Predicate | cityDistance |
P7750
|
FINISHED |
| Object | about 11 kilometers west of Hyderabad city center |
—
|
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: about 11 kilometers west of Hyderabad city center | Statement: [Golconda Fort, cityDistance, about 11 kilometers west of Hyderabad city center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityDistance Context triple: [Golconda Fort, cityDistance, about 11 kilometers west of Hyderabad city center]
-
A.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
-
B.
distance
chosen
Indicates the spatial separation or length between two points, objects, or locations.
-
C.
distanceFromLosAngeles
Indicates the measured or specified distance between a given entity’s location and the city of Los Angeles.
-
D.
distanceToLosAngeles
Indicates the measured or calculated distance between a given entity’s location and the city of Los Angeles.
-
E.
betweenCity
Indicates a spatial relationship where one entity is located in the area or position separating two specified cities.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9c3300881909f5c3544f8923b41 |
completed | March 8, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.