Triple
T124651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campaign for Nuclear Disarmament |
E2520
|
entity |
| Predicate | positionOnNATO |
P4943
|
FINISHED |
| Object | opposes nuclear policies of NATO |
—
|
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: opposes nuclear policies of NATO | Statement: [Campaign for Nuclear Disarmament, positionOnNATO, opposes nuclear policies of NATO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnNATO Context triple: [Campaign for Nuclear Disarmament, positionOnNATO, opposes nuclear policies of NATO]
-
A.
isNATOAllyOf
Indicates that one entity is a member of NATO and has a formal alliance relationship with the other entity within the NATO framework.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
locatedNorthOf
Indicates that one entity is positioned geographically to the north of another entity.
-
D.
strategicLocation
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
-
E.
locatedEastOf
Indicates that one entity is positioned geographically to the east of another entity.
- 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_69a251b54ea88190b18281669f59b4c0 |
completed | Feb. 28, 2026, 2:23 a.m. |
| NER | Named-entity recognition | batch_69a2573e4e6481908252dfef2e34f46e |
completed | Feb. 28, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69a2564a54948190ba30bee858173b27 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a256ea776081908fec36c3fdfb8d84 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:27 a.m.