Triple
T4352488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander Field Army |
E98058
|
entity |
| Predicate | usedInConflictType |
P55719
|
FINISHED |
| Object | expeditionary operations |
—
|
LITERAL FINISHED |
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: expeditionary operations | Statement: [Commander Field Army, usedInConflictType, expeditionary operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInConflictType Context triple: [Commander Field Army, usedInConflictType, expeditionary operations]
-
A.
conflictUse
Indicates a relationship where one entity’s use, application, or operation is incompatible with, obstructs, or negatively interferes with another entity’s use.
-
B.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
C.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
D.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
E.
namedForConflict
Indicates that one entity is named after, or in commemoration of, a specific conflict, war, or battle.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351ab03488190a8900de98fb4a00e |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:15 p.m.