Triple
T29967638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellavista |
E761231
|
entity |
| Predicate | distanceToPuertoAyora |
P202816
|
FINISHED |
| Object | approximately 7 km |
—
|
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 7 km | Statement: [Bellavista, distanceToPuertoAyora, approximately 7 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToPuertoAyora Context triple: [Bellavista, distanceToPuertoAyora, approximately 7 km]
-
A.
distanceToPraia
Indicates the measured distance between an entity and the location Praia.
-
B.
distanceFromPagoPago
Indicates the spatial distance between a given entity and the location of Pago Pago.
-
C.
distanceFromPuertoRioTranquilo
Indicates the measured distance between an entity and Puerto Río Tranquilo.
-
D.
distanceToBerlengas
Indicates the measured distance between a given entity’s location and the Berlengas.
-
E.
distanceFromPuertoPrincesaKilometers
Indicates the physical distance, measured in kilometers, between a given location and Puerto Princesa.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a00bf5990e08190a8b633e237656564 |
completed | May 10, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_6a00beef4f5881909b00ac89e6af5902 |
completed | May 10, 2026, 5:22 p.m. |
| PDg | Predicate description generation | batch_6a00bf5899b08190ad012a0879907d65 |
completed | May 10, 2026, 5:24 p.m. |
Created at: April 29, 2026, 6:30 p.m.