Triple
T15232769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euron Greyjoy |
E364045
|
entity |
| Predicate | usurps |
P65651
|
FINISHED |
| Object | Balon Greyjoy’s throne |
—
|
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: Balon Greyjoy’s throne | Statement: [Euron Greyjoy, usurps, Balon Greyjoy’s throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usurps Context triple: [Euron Greyjoy, usurps, Balon Greyjoy’s throne]
-
A.
usurpedFrom
Indicates that one entity has taken power, position, or property from another entity illegitimately or by force.
-
B.
usurpsThroneFrom
chosen
Indicates that one entity seizes control of a throne or rulership position that previously belonged to another entity, typically by force or illegitimate means.
-
C.
usurperInRegion
Indicates that an entity has unlawfully taken or holds power or authority within a specified region.
-
D.
suzerain
Indicates a relationship in which one entity holds overlordship or supreme authority over another, which remains internally autonomous but owes allegiance, tribute, or obedience.
-
E.
usurperOnLosingSide
Indicates that the usurper was aligned with the faction or side that ultimately lost in a conflict or power struggle.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007d7237081908dc17900ee66b64f |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.