Triple
T38643553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Throne of the Four Winds |
E938661
|
entity |
| Predicate | associatedElementalLord |
P47636
|
FINISHED |
| Object | Al’Akir |
E2276801
|
NE 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: Al’Akir | Statement: [Throne of the Four Winds, associatedElementalLord, Al’Akir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedElementalLord Context triple: [Throne of the Four Winds, associatedElementalLord, Al’Akir]
-
A.
lordOf
chosen
Indicates that one entity holds lordship, authority, or dominion over another entity.
-
B.
borderLord
Indicates that one entity serves as the feudal or territorial lord presiding over a border or frontier region associated with another entity.
-
C.
spiritualConsortOf
Indicates a relationship in which one entity is regarded as the spiritual or sacred partner, counterpart, or consort of another.
-
D.
associatedDeityOrForce
Indicates that one entity is linked to, represented by, or under the influence of a particular deity or supernatural force.
-
E.
overlordPower
Indicates that one entity holds dominant, controlling authority or power over another, often in a hierarchical or oppressive manner.
- F. None of above.
Provenance (4 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4205b84ba881908ea5c4ff8becc791 |
completed | June 29, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.