Triple
T3648317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puerto Ayacucho |
E77355
|
entity |
| Predicate | distanceToCapitalCity |
P10889
|
FINISHED |
| Object | approx. 700 km south-southwest of Caracas |
—
|
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: approx. 700 km south-southwest of Caracas | Statement: [Puerto Ayacucho, distanceToCapitalCity, approx. 700 km south-southwest of Caracas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToCapitalCity Context triple: [Puerto Ayacucho, distanceToCapitalCity, approx. 700 km south-southwest of Caracas]
-
A.
distanceFromCapital
chosen
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
B.
stateCapitalProximity
Indicates the spatial closeness or distance between a state’s capital city and another specified location.
-
C.
districtHeadquartersDistance
Indicates the distance between a place and its corresponding district headquarters.
-
D.
countryCapitalNearby
Indicates that a country’s capital city is geographically close to a specified location or entity.
-
E.
regionCapitalNearby
Indicates that a capital city of a region is located close to the referenced place or entity.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc38c22548190a271a69fb832a5a8 |
completed | March 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.