Triple
T4204578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Plata |
E86152
|
entity |
| Predicate | distanceToBuenosAires |
P23952
|
FINISHED |
| Object | approximately 60 km southeast |
—
|
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 60 km southeast | Statement: [La Plata, distanceToBuenosAires, approximately 60 km southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBuenosAires Context triple: [La Plata, distanceToBuenosAires, approximately 60 km southeast]
-
A.
distanceFromBuenosAires
chosen
Indicates the measured distance between a given entity’s location and the city of Buenos Aires.
-
B.
distanceToSantiago_km
Indicates the physical distance, measured in kilometers, between a given location and Santiago.
-
C.
widthNearBuenosAires
Indicates that an entity’s width measurement is geographically close to, or approximately aligned with, the width at the location of Buenos Aires.
-
D.
distanceFromPotosiApproximate
Indicates an approximate measure of how far something is from Potosi.
-
E.
distanceToSouthAmerica
Indicates the spatial distance between a given entity’s location and the continent of South America.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0382eafc8190946bf45bf28095dd |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:49 p.m.