Triple
T25361309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friedrich Wilhelm von Buxhoeveden |
E635973
|
entity |
| Predicate | heldCommandInConflictWith |
P158233
|
FINISHED |
| Object | France |
—
|
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: France | Statement: [Friedrich Wilhelm von Buxhoeveden, heldCommandInConflictWith, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldCommandInConflictWith Context triple: [Friedrich Wilhelm von Buxhoeveden, heldCommandInConflictWith, France]
-
A.
heldCommandInConflictWith
chosen
Indicates that one entity exercised command authority over another entity or group while engaged in an armed conflict or war.
-
B.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
C.
parallelCommandHeldBy
Indicates that a command or authority is concurrently exercised or held by multiple entities at the same time.
-
D.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
-
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_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_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:36 p.m.