Triple
T11211814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jinotepe |
E265326
|
entity |
| Predicate | distanceFromCapitalCity |
P10889
|
FINISHED |
| Object | approximately 45 km south of Managua |
—
|
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 45 km south of Managua | Statement: [Jinotepe, distanceFromCapitalCity, approximately 45 km south of Managua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromCapitalCity Context triple: [Jinotepe, distanceFromCapitalCity, approximately 45 km south of Managua]
-
A.
distanceFromCapital
chosen
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
B.
prefectureCapitalDistance
Indicates the distance between a prefecture and its designated capital city.
-
C.
regionCapitalDistanceRelation
Indicates a relationship specifying the distance between a region and its capital.
-
D.
distanceToDepartmentCapital
Indicates the measured distance between a given location and the capital city of its corresponding department.
-
E.
distanceFromMajorCity
Indicates the measured distance between a given location and a specified major city.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d6f5d4819086dcb776a0d469e8 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.