Triple
T1550112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German occupation of Dunkirk |
E33069
|
entity |
| Predicate | natureOfStatement |
P31143
|
FINISHED |
| Object | historical event |
—
|
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: historical event | Statement: [German occupation of Dunkirk, natureOfStatement, historical event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natureOfStatement Context triple: [German occupation of Dunkirk, natureOfStatement, historical event]
-
A.
statement
Indicates that an entity makes, issues, or expresses a declarative assertion, claim, or remark about something.
-
B.
bindingNatureOfJudgments
Indicates that judgments or decisions have a compulsory, legally enforceable effect on the parties or entities to which they apply.
-
C.
lawStatement
Indicates that an entity expresses, codifies, or articulates a legal rule, principle, or requirement.
-
D.
policyStance
Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
-
E.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa574094048190a2d7fc3ac904d51e |
completed | March 6, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69a907b426dc8190975c024a50955368 |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69aa573ee8e0819084abf59f1ddbd1da |
completed | March 6, 2026, 4:25 a.m. |
Created at: March 4, 2026, 7:26 p.m.