Triple
T14331193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Peru |
E355349
|
entity |
| Predicate | relativeLocationToUpperPeru |
P114001
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [Lower Peru, relativeLocationToUpperPeru, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeLocationToUpperPeru Context triple: [Lower Peru, relativeLocationToUpperPeru, south]
-
A.
regionOnPeruSide
Indicates that a region is located on the side of a boundary or border that belongs to or is associated with Peru.
-
B.
directionFromCusco
Indicates the cardinal or relative direction in which one entity is located from the reference point of Cusco.
-
C.
distanceFromLima
Indicates the measured distance between a given place or object and the city of Lima.
-
D.
hasRelativePositionToLicancabur
Indicates that one entity has a specific spatial or geographic position defined in relation to Licancabur.
-
E.
distanceFromLaPazApproximate
Indicates an approximate measure of how far something is from La Paz, typically expressed as a rough distance rather than an exact value.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c1def0081908f03cda8e84d20c0 |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e9ded24819099200349cf80e068 |
completed | April 14, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:13 a.m.