Triple
T1657267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Expeditionary Force (World War II) |
E35827
|
entity |
| Predicate | withdrawalCompleted |
P12347
|
FINISHED |
| Object | June 1940 |
—
|
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: June 1940 | Statement: [British Expeditionary Force (World War II), withdrawalCompleted, June 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withdrawalCompleted Context triple: [British Expeditionary Force (World War II), withdrawalCompleted, June 1940]
-
A.
withdrawalAnnouncedBy
Indicates that an entity’s withdrawal (e.g., from an agreement, position, or situation) has been publicly announced or declared by a specified agent or source.
-
B.
withdrewFrom
Indicates that one entity removed itself or its participation from another entity, context, or arrangement it was previously part of.
-
C.
withdrawalDate
chosen
Indicates the date on which a withdrawal action occurs or is recorded.
-
D.
reasonForWithdrawal
Indicates the cause, motive, or circumstance that explains why a withdrawal occurred.
-
E.
hasWithdrawalClause
Indicates that an agreement or contract includes a provision specifying how a party may withdraw or terminate their participation.
- 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_69a88606aa808190aa0b421b4271f220 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69a907cff53c8190b424f088478d3e2c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.