Triple
T26851229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larrea–Gual Treaty |
E676062
|
entity |
| Predicate | conflictSettled |
P4546
|
FINISHED |
| Object | Gran Colombia–Peru War |
—
|
NE NERFINISHED |
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: Gran Colombia–Peru War | Statement: [Larrea–Gual Treaty, conflictSettled, Gran Colombia–Peru War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictSettled Context triple: [Larrea–Gual Treaty, conflictSettled, Gran Colombia–Peru War]
-
A.
conflictResolvedBy
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
-
B.
conflictResult
Indicates the outcome or consequence that arises from a particular conflict between entities.
-
C.
settledAs
Indicates that one entity has been resolved, finalized, or agreed upon in the form or status of another entity.
-
D.
endedConflict
chosen
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
E.
conflictedBetween
Indicates being torn or uncertain between two or more options, positions, or commitments.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:17 a.m.