Triple
T607716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finland |
E12029
|
entity |
| Predicate | coldWarPolicy |
P1422
|
FINISHED |
| Object | military non-alignment |
—
|
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: military non-alignment | Statement: [Finland, coldWarPolicy, military non-alignment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coldWarPolicy Context triple: [Finland, coldWarPolicy, military non-alignment]
-
A.
statusDuringColdWar
chosen
Indicates the political or diplomatic status or alignment that an entity held specifically during the Cold War period.
-
B.
statusAfterColdWar
Indicates the condition or standing of an entity in the period following the end of the Cold War.
-
C.
maintainedPeaceWith
Indicates that two entities sustained a state of peace or non-conflict with each other over a period of time.
-
D.
foreignPolicyContext
Indicates the broader international relations setting or circumstances within which a foreign policy decision, action, or stance occurs.
-
E.
endedBilateralWarBetween
Indicates that an action or event brought a bilateral war between two parties to a conclusion or cessation.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49df34abc8190a578c8c2ab3d28e4 |
completed | March 1, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69a49cf8fc1c81908a9c7df552aa1a59 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.