Triple
T13039775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbia and Bulgaria |
E327159
|
entity |
| Predicate | postColdWarRelation |
P16561
|
FINISHED |
| Object | normalized relations |
—
|
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: normalized relations | Statement: [Serbia and Bulgaria, postColdWarRelation, normalized relations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postColdWarRelation Context triple: [Serbia and Bulgaria, postColdWarRelation, normalized relations]
-
A.
statusDuringColdWar
Indicates the political or diplomatic status or alignment that an entity held specifically during the Cold War period.
-
B.
statusAfterColdWar
chosen
Indicates the condition or standing of an entity in the period following the end of the Cold War.
-
C.
partOfColdWarContext
Indicates that something occurs within, contributes to, or is significantly shaped by the geopolitical, ideological, or military dynamics of the Cold War period.
-
D.
coldWarAdversary
Indicates that two entities were opposing geopolitical rivals during the Cold War era.
-
E.
roleDuringColdWar
Indicates the specific position, function, or involvement an entity had in the context of the Cold War period.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:55 p.m.