Triple
T21756696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecuador–Peru border in the Cordillera del Cóndor |
E537058
|
entity |
| Predicate | finalDemarcationCompleted |
P135621
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Ecuador–Peru border in the Cordillera del Cóndor, finalDemarcationCompleted, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalDemarcationCompleted Context triple: [Ecuador–Peru border in the Cordillera del Cóndor, finalDemarcationCompleted, 1998]
-
A.
closureCompleted
Indicates that a previously initiated closure process or shutdown has been fully and successfully completed.
-
B.
finalPhaseOf
Indicates that one process, stage, or event constitutes the concluding or last phase of another broader process or sequence.
-
C.
completionOf
chosen
Indicates that one entity represents the finished state, fulfillment, or successful conclusion of another entity, process, or requirement.
-
D.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
-
E.
deploymentEnd
Indicates the point in time or event at which a deployment process or deployment state comes to an end.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8ea04c8190a8c4fa43b3f23935 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969e46088190b13d6e9025775ea3 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.