Triple
T7711957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Saxony |
E174780
|
entity |
| Predicate | changedAllegiance |
P12199
|
FINISHED |
| Object | Coalition powers after 1813 |
—
|
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: Coalition powers after 1813 | Statement: [Kingdom of Saxony, changedAllegiance, Coalition powers after 1813]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedAllegiance Context triple: [Kingdom of Saxony, changedAllegiance, Coalition powers after 1813]
-
A.
hadAllegiance
Indicates that an entity was loyally committed or formally bound in support or service to another entity, such as a person, group, or cause.
-
B.
changesAllianceOf
Indicates that one entity causes or initiates a change in the alliance or affiliation status of another entity.
-
C.
allegiance
Indicates a relationship where one entity is loyal, committed, or obligated in support or service to another entity.
-
D.
defectedTo
chosen
Indicates that an entity abandoned its original side, group, or allegiance and joined or gave support to another, typically opposing, side.
-
E.
protagonistAllegiance
Indicates the group, cause, or side with which the main character is aligned or to which they show loyalty.
- 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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:04 p.m.