Triple
T1082070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playa del Carmen |
E23967
|
entity |
| Predicate | distanceToCancun |
P23730
|
FINISHED |
| Object | approximately 68 kilometers south |
—
|
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 68 kilometers south | Statement: [Playa del Carmen, distanceToCancun, approximately 68 kilometers south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToCancun Context triple: [Playa del Carmen, distanceToCancun, approximately 68 kilometers south]
-
A.
distanceToSanDiego
Indicates the measured or estimated distance between a given entity’s location and the city of San Diego.
-
B.
distanceToSantaMarta
Indicates the measured spatial distance between a given entity’s location and the location of Santa Marta.
-
C.
distanceFromCusco
Indicates the measured spatial distance between a given location or entity and the city of Cusco.
-
D.
distanceToLosAngeles
Indicates the measured or calculated distance between a given entity’s location and the city of Los Angeles.
-
E.
distanceToKingstonApprox
Indicates an approximate distance between a given location and Kingston.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b95d35888190a20593a278175df7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73f4310819086281f8ec67d1a32 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b80f0fb08190a19a50e38ae8f16c |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.