Triple
T25361308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friedrich Wilhelm von Buxhoeveden |
E635973
|
entity |
| Predicate | heldCommandInConflictWith |
P158233
|
FINISHED |
| Object | Sweden |
—
|
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: Sweden | Statement: [Friedrich Wilhelm von Buxhoeveden, heldCommandInConflictWith, Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldCommandInConflictWith Context triple: [Friedrich Wilhelm von Buxhoeveden, heldCommandInConflictWith, Sweden]
-
A.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
B.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
-
C.
conflictedBetween
Indicates being torn or uncertain between two or more options, positions, or commitments.
-
D.
operatorBeforeConflict
Indicates that an operator performed or was in place before a specified conflict occurred or was identified.
-
E.
supportedConflict
Indicates that one party provided assistance, resources, or endorsement to a side involved in a conflict or dispute.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4a10a013481908a43dd0c23917c48 |
completed | May 1, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 1:36 p.m.