Triple
T21096700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gumaca, Quezon |
E519785
|
entity |
| Predicate | distanceToLucenaCity_km |
P142837
|
FINISHED |
| Object | approximately 95 |
—
|
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 95 | Statement: [Gumaca, Quezon, distanceToLucenaCity_km, approximately 95]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLucenaCity_km Context triple: [Gumaca, Quezon, distanceToLucenaCity_km, approximately 95]
-
A.
distanceFromCórdobaCity
Indicates the spatial distance between an entity and the city of Córdoba.
-
B.
distanceToValladolid
Indicates the spatial distance between a given entity or location and the city of Valladolid.
-
C.
distanceToMérida
Indicates the spatial distance between a given entity and the location Mérida.
-
D.
distanceFromSeville
Indicates the spatial distance separating an entity from the location of Seville.
-
E.
distanceToNeuquénCity_km
Indicates the physical distance, measured in kilometers, between an entity and the city of Neuquén.
- 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b595cdc8190ba7a6f3f71d40c3f |
completed | April 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:52 p.m.