Triple
T368864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plan White |
E8222
|
entity |
| Predicate | coincidedWith |
P4881
|
FINISHED |
| Object | United Kingdom declaration of war on Germany |
—
|
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: United Kingdom declaration of war on Germany | Statement: [Plan White, coincidedWith, United Kingdom declaration of war on Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coincidedWith Context triple: [Plan White, coincidedWith, United Kingdom declaration of war on Germany]
-
A.
coincidesWith
chosen
Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
-
B.
meetsDuring
Indicates that one entity encounters or comes together with another while a specified event or time interval is in progress.
-
C.
occurredDuring
Indicates that one event or action took place within the temporal span of another event or time period.
-
D.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
E.
observesSameTimeAs
Indicates that two observation events occur simultaneously or during the same time interval.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebeab13c8190b15c2f10310ec6a8 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95ede588190998fdf3a6ea90498 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.