Triple
T38289605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamningberg |
E1022320
|
entity |
| Predicate | notDestroyedDuring |
P179678
|
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: [Hamningberg, notDestroyedDuring, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notDestroyedDuring Context triple: [Hamningberg, notDestroyedDuring, World War II]
-
A.
neverDestroyed
Indicates that the entity has not been destroyed at any point in time and remains intact or existent throughout the relevant period.
-
B.
possiblyDestroyedIn
Indicates that an entity may have been destroyed during or as a result of a specified event or situation.
-
C.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
D.
avoidedDestructionIn
chosen
Indicates that an entity narrowly escaped being destroyed during a particular event, time, or situation.
-
E.
destroyedAfter
Indicates that one entity is destroyed at a point in time that occurs after the destruction of another entity.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.