Triple
T35165370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B 18 |
E1015386
|
entity |
| Predicate | usedAfterConflict |
P197181
|
FINISHED |
| Object | post–World War II period |
—
|
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: post–World War II period | Statement: [B 18, usedAfterConflict, post–World War II period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAfterConflict Context triple: [B 18, usedAfterConflict, post–World War II period]
-
A.
usedByDuringConflict
Indicates that one entity made practical use of another entity specifically in the context of a particular conflict or war.
-
B.
subsequentConflict
Indicates that one conflict occurs after and is temporally subsequent to another conflict.
-
C.
basedOnConflict
Indicates that one entity is derived from, influenced by, or structured around a particular conflict involving another entity.
-
D.
usedInConflictPhase
Indicates that an action, resource, or strategy is employed during a specific phase or stage of a conflict.
-
E.
implementedDuringConflict
Indicates that an action, policy, or measure was carried out while an active conflict or war was ongoing.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69fe7b1b3460819081172731b52ac15b |
completed | May 9, 2026, 12:08 a.m. |
Created at: May 3, 2026, 4:02 p.m.