Triple
T23461820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nauta |
E568998
|
entity |
| Predicate | distanceToIquitos_km |
P152361
|
FINISHED |
| Object | approximately 95 |
—
|
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 95 | Statement: [Nauta, distanceToIquitos_km, approximately 95]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToIquitos_km Context triple: [Nauta, distanceToIquitos_km, approximately 95]
-
A.
distanceFromLima
Indicates the measured distance between a given place or object and the city of Lima.
-
B.
distanceToGuayaquil_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Guayaquil.
-
C.
distanceFromCusco
Indicates the measured spatial distance between a given location or entity and the city of Cusco.
-
D.
distanceFromHuaraz
Indicates the spatial distance between an entity and the location of Huaraz.
-
E.
distanceFromArequipa
Indicates the spatial distance between a given location and the city of Arequipa.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a69bc200819096ed2baf25cdee4f |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:54 p.m.