Triple
T19227652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinguiririca Volcano |
E480780
|
entity |
| Predicate | distanceFromSanFernando |
P135258
|
FINISHED |
| Object | approximately 80 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 80 km southeast | Statement: [Tinguiririca Volcano, distanceFromSanFernando, approximately 80 km southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromSanFernando Context triple: [Tinguiririca Volcano, distanceFromSanFernando, approximately 80 km southeast]
-
A.
distanceFromSanJosé
Indicates the measured spatial distance between a given entity and the location of San José.
-
B.
distanceToFresno
Indicates the physical distance between a given location or entity and the city of Fresno.
-
C.
distanceToSanBernardino
Indicates the measured distance between a given entity’s location and the location of San Bernardino.
-
D.
distanceToSanJosé
Indicates the spatial distance between a given entity and the location of San José.
-
E.
distanceFromSanFrancisco
Indicates the measured distance between a given entity’s location and the city of San Francisco.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa9968e88190b14844715ff3aa2a |
completed | April 20, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4debc39ac81908b7c5ef797046360 |
completed | April 19, 2026, 1:55 p.m. |
Created at: April 10, 2026, 1:25 p.m.