Triple
T16340978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Jose, Negros Oriental |
E396802
|
entity |
| Predicate | distanceToDumagueteCity |
P123039
|
FINISHED |
| Object | approximately 14 kilometers |
—
|
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 14 kilometers | Statement: [San Jose, Negros Oriental, distanceToDumagueteCity, approximately 14 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDumagueteCity Context triple: [San Jose, Negros Oriental, distanceToDumagueteCity, approximately 14 kilometers]
-
A.
distanceToDavaoCity
Indicates the measured distance between a given entity’s location and Davao City.
-
B.
distanceFromDavaoCity
Indicates the measured spatial distance between a given location and Davao City.
-
C.
approxDistanceFromCebuCity
Indicates that one entity is located at an approximate distance from Cebu City.
-
D.
distanceFromManila
Indicates the measured spatial distance between a given entity’s location and the city of Manila.
-
E.
distanceToIloiloCityCenter_km
Indicates the physical distance, measured in kilometers, from an entity’s location to the center of Iloilo City.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da09dcf48190b6fdd14b1812c56a |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:07 a.m.