Triple
T3181178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Bulgaria |
E66588
|
entity |
| Predicate | switchedPolicy |
P9880
|
FINISHED |
| Object | withdrew from Axis in 1944 |
—
|
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: withdrew from Axis in 1944 | Statement: [Kingdom of Bulgaria, switchedPolicy, withdrew from Axis in 1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: switchedPolicy Context triple: [Kingdom of Bulgaria, switchedPolicy, withdrew from Axis in 1944]
-
A.
changePolicy
Indicates that an entity modifies, replaces, or updates an existing policy governing rules, procedures, or behaviors.
-
B.
policyShift
chosen
Indicates a change or adjustment in an existing policy, typically reflecting a new direction, priority, or approach.
-
C.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
-
D.
replacedPolicyApproach
Indicates that one policy approach has been superseded and taken the place of another policy approach.
-
E.
advancedPolicyOf
Indicates that one policy is a more developed, detailed, or progressive version of another policy.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6a1280c8190b59a2afd30312c02 |
completed | March 8, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.