Triple
T15317644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opposition Bloc |
E366202
|
entity |
| Predicate | stanceOnNATO |
P118087
|
FINISHED |
| Object | opposes Ukraine’s NATO membership |
—
|
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 Ukraine’s NATO membership | Statement: [Opposition Bloc, stanceOnNATO, opposes Ukraine’s NATO membership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stanceOnNATO Context triple: [Opposition Bloc, stanceOnNATO, opposes Ukraine’s NATO membership]
-
A.
moveOfNATOFrom
Indicates a movement or deployment action carried out by NATO originating from a specified location.
-
B.
roleInNATO
Indicates the specific capacity, position, or function an entity holds within the organizational or operational structure of NATO.
-
C.
NATOCategory
Indicates that an entity is classified according to a specific NATO-defined category or designation.
-
D.
NATOCooperationSuspended
Indicates that cooperative activities or partnerships with NATO have been halted or put on hold between the involved parties.
-
E.
NATOCooperationSuspensionReason
Indicates the reason why cooperation with NATO has been suspended between the involved parties.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd1d384819098f38402a8740d91 |
completed | April 16, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:16 a.m.