Triple
T25238020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilson governments |
E632388
|
entity |
| Predicate | defencePolicy |
P161637
|
FINISHED |
| Object | withdrawal from East of Suez commitments |
—
|
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: withdrawal from East of Suez commitments | Statement: [Wilson governments, defencePolicy, withdrawal from East of Suez commitments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defencePolicy Context triple: [Wilson governments, defencePolicy, withdrawal from East of Suez commitments]
-
A.
providesDefence
Indicates that one entity offers protection or defensive support to another entity.
-
B.
defenceCategory
Indicates a classification relationship where an entity is assigned to a specific type or category of defence.
-
C.
defenceBody
Indicates a relationship where an entity serves as the official body or organization responsible for defense or military affairs of another entity (such as a country or jurisdiction).
-
D.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
E.
defenseStatus
Indicates the current state or condition of an entity’s defensive posture or protective readiness in a given context.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6200ac60481909895c61d050b1338 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 21, 2026, 1:07 p.m.