Triple
T33131656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Mateo, Rizal |
E847887
|
entity |
| Predicate | distanceToQuezonCity |
P206362
|
FINISHED |
| Object | about 11 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: about 11 kilometers | Statement: [San Mateo, Rizal, distanceToQuezonCity, about 11 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToQuezonCity Context triple: [San Mateo, Rizal, distanceToQuezonCity, about 11 kilometers]
-
A.
distanceFromManila
Indicates the measured spatial distance between a given entity’s location and the city of Manila.
-
B.
distanceFromDavaoCity
Indicates the measured spatial distance between a given location and Davao City.
-
C.
distanceToDavaoCity
Indicates the measured distance between a given entity’s location and Davao City.
-
D.
approxDistanceFromCebuCity
Indicates that one entity is located at an approximate distance from Cebu City.
-
E.
distanceToMalolos
Indicates the spatial distance between a given entity and the location of Malolos.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:27 a.m.