Triple
T506786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yugoslavia |
E10518
|
entity |
| Predicate | allianceStatus |
P14509
|
FINISHED |
| Object | non-aligned |
—
|
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: non-aligned | Statement: [Yugoslavia, allianceStatus, non-aligned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allianceStatus Context triple: [Yugoslavia, allianceStatus, non-aligned]
-
A.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
-
B.
allianceMember
Indicates that an entity is a member or participant in a specific alliance or coalition.
-
C.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
D.
allianceRole
Indicates the specific function, status, or responsibility an entity holds within an alliance or cooperative partnership.
-
E.
allianceUse
Indicates that one party makes use of, benefits from, or leverages an alliance or allied relationship with another party.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f14c83f08190b1028f4929866db4 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfce7a08190a408bc019de60d5d |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebbd70481908b462296671de67b |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.