Triple
T22726451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poland and Czech Republic |
E562005
|
entity |
| Predicate | shareSecurityFramework |
P10771
|
FINISHED |
| Object | NATO collective defense |
—
|
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: NATO collective defense | Statement: [Poland and Czech Republic, shareSecurityFramework, NATO collective defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareSecurityFramework Context triple: [Poland and Czech Republic, shareSecurityFramework, NATO collective defense]
-
A.
protectionFramework
Indicates a relationship where one entity establishes or provides a structured set of rules, measures, or mechanisms designed to protect another entity or its interests.
-
B.
includesRegionalSecurityFramework
Indicates that an entity incorporates or is part of a broader regional security cooperation or defense framework.
-
C.
securityPillar
Indicates that one entity functions as a foundational security pillar or core security domain in relation to another entity.
-
D.
securityAlliance
chosen
Indicates a formal cooperative relationship in which entities agree to support and protect each other’s security interests, often including mutual defense or coordinated security measures.
-
E.
hasSecurityArchitecture
Indicates that an entity is associated with or defined by a particular security architecture design or framework.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1792a2ee48190bfbdde1a72adfd25 |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:20 p.m.