Triple
T24550350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pataz |
E607344
|
entity |
| Predicate | distanceToRegionCapital |
P79023
|
FINISHED |
| Object | remote from Trujillo |
—
|
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: remote from Trujillo | Statement: [Pataz, distanceToRegionCapital, remote from Trujillo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToRegionCapital Context triple: [Pataz, distanceToRegionCapital, remote from Trujillo]
-
A.
distanceFromRegionalCapital
Indicates the measured spatial distance between a given place and its corresponding regional capital.
-
B.
distanceFromCapital
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
C.
distanceToProvinceCapital_km
Indicates the distance, measured in kilometers, between a given location and the capital city of its province.
-
D.
distanceToDepartmentCapital
Indicates the measured distance between a given location and the capital city of its corresponding department.
-
E.
regionCapitalDistanceRelation
chosen
Indicates a relationship specifying the distance between a region and its capital.
- F. None of above.
Provenance (3 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_69e2c4cae1b88190825e88d5ce8aa61e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8ccddec8190819e6366b3d6b6f0 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.