Triple
T25563182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO |
E640768
|
entity |
| Predicate | hasPartnershipProgram |
P169215
|
FINISHED |
| Object | Partnership for Peace |
—
|
NE NERFINISHED |
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: Partnership for Peace | Statement: [NATO, hasPartnershipProgram, Partnership for Peace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartnershipProgram Context triple: [NATO, hasPartnershipProgram, Partnership for Peace]
-
A.
hasPartnershipType
Indicates the specific kind or category of partnership relationship that exists between entities.
-
B.
hasCoopPrograms
Indicates that an entity offers or participates in cooperative education programs in partnership with other organizations or institutions.
-
C.
hasPartnershipRole
Indicates that an entity holds a specific role or function within a partnership relationship with another entity.
-
D.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
E.
hasContributorProgram
Indicates that an entity operates or participates in a formal program through which contributors can submit work, content, or support.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67c9ec1708190b26ccf402ed7b106 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 21, 2026, 3:47 p.m.