Triple
T502656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Ivanhoe |
E10431
|
entity |
| Predicate | serviceStartConflict |
P14454
|
FINISHED |
| Object | early years of World War II |
—
|
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: early years of World War II | Statement: [HMS Ivanhoe, serviceStartConflict, early years of World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceStartConflict Context triple: [HMS Ivanhoe, serviceStartConflict, early years of World War II]
-
A.
supportedConflict
Indicates that one party provided assistance, resources, or endorsement to a side involved in a conflict or dispute.
-
B.
reasonForConflict
Indicates that one entity is the cause, motive, or underlying issue leading to a conflict involving another entity.
-
C.
previousConflict
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
-
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.
subsequentConflict
Indicates that one conflict occurs after and is temporally subsequent to another conflict.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1339748819089f89691a1698dd9 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfbb7e0819092cf29c2c68fe8fb |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebbd70481908b462296671de67b |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.