Triple
T36143763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bombing of Himmel Street |
E1045386
|
entity |
| Predicate | occursDuringConflict |
P49719
|
FINISHED |
| Object | World War II |
—
|
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: World War II | Statement: [bombing of Himmel Street, occursDuringConflict, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursDuringConflict Context triple: [bombing of Himmel Street, occursDuringConflict, World War II]
-
A.
usedByDuringConflict
Indicates that one entity made practical use of another entity specifically in the context of a particular conflict or war.
-
B.
conflictsOccurIn
Indicates that one or more conflicts take place within, or are situated in, a specified context, location, or setting.
-
C.
implementedDuringConflict
chosen
Indicates that an action, policy, or measure was carried out while an active conflict or war was ongoing.
-
D.
conflictPeriod
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
E.
existedDuringConflict
Indicates that an entity was present or active for some or all of the duration of a specified conflict.
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:08 p.m.