Triple
T34434185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO partnerships |
E883908
|
entity |
| Predicate | hasPartnerCategory |
P15570
|
FINISHED |
| Object | Euro-Atlantic partners |
—
|
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: Euro-Atlantic partners | Statement: [NATO partnerships, hasPartnerCategory, Euro-Atlantic partners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartnerCategory Context triple: [NATO partnerships, hasPartnerCategory, Euro-Atlantic partners]
-
A.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
B.
hasPartnershipType
chosen
Indicates the specific kind or category of partnership relationship that exists between entities.
-
C.
hasPartnerOrganization
Indicates that an entity is formally associated or collaborates with another entity as a partner organization.
-
D.
hasExPartner
Indicates that one entity was formerly in a romantic or intimate partnership with another entity, but that relationship has ended.
-
E.
hasPartnerDesignation
Indicates that one entity is formally designated as a partner of another entity within a specified context or relationship.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff84df768c81908c65a1a7e33103ad |
completed | May 9, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69ff848d0af881908ee42c27a58af47e |
completed | May 9, 2026, 7:01 p.m. |
Created at: May 1, 2026, 2 a.m.