Triple
T28463538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlos Saavedra Lamas |
E720223
|
entity |
| Predicate | mediatedConflict |
P58467
|
FINISHED |
| Object | Chaco 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: Chaco War | Statement: [Carlos Saavedra Lamas, mediatedConflict, Chaco War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediatedConflict Context triple: [Carlos Saavedra Lamas, mediatedConflict, Chaco War]
-
A.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
B.
mediatedIn
chosen
Indicates that an entity acted as an intermediary or facilitator in bringing about, enabling, or influencing another entity or event.
-
C.
mediumOfConflict
Indicates the channel, environment, or means through which a conflict is conducted or expressed.
-
D.
conflictIntended
Indicates that one entity deliberately aims to oppose, obstruct, or create conflict with another entity or its goals.
-
E.
facedConflictOver
Indicates that two or more entities experienced opposition, dispute, or tension concerning a particular issue, resource, or situation.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:42 a.m.