Triple
T23543440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of 1824 with the United States |
E577817
|
entity |
| Predicate | partyInConflict |
P95241
|
FINISHED |
| Object | United States government |
—
|
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: United States government | Statement: [Treaty of 1824 with the United States, partyInConflict, United States government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyInConflict Context triple: [Treaty of 1824 with the United States, partyInConflict, United States government]
-
A.
partnerInConflictWith
chosen
Indicates that two entities are engaged as opposing partners or sides within the same conflict or dispute.
-
B.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
-
C.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
D.
politicalConflict
Indicates a relationship where entities are engaged in opposing political positions, struggles, or disputes, often involving competition for power, influence, or policy outcomes.
-
E.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1dbe188190bc4afe7bfa7cda0f |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.