Triple
T34729959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Officer Commanding III Corps |
E1001179
|
entity |
| Predicate | holderConflict |
P181807
|
FINISHED |
| Object | World War II 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: World War II operations | Statement: [General Officer Commanding III Corps, holderConflict, World War II operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderConflict Context triple: [General Officer Commanding III Corps, holderConflict, World War II operations]
-
A.
valueConflict
Indicates a situation where two or more values, preferences, or principles are in opposition or cannot be simultaneously satisfied.
-
B.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
C.
mentionsConflict
Indicates that one entity refers to or discusses a dispute, disagreement, or conflict involving another entity.
-
D.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
E.
captureConflict
Indicates that one entity records, represents, or encapsulates a conflict involving another entity or between multiple entities.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: May 3, 2026, 3:59 p.m.