Triple
T2282818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odin |
E51318
|
entity |
| Predicate | canSeeFromThrone |
P36253
|
FINISHED |
| Object | all nine worlds |
—
|
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: all nine worlds | Statement: [Odin, canSeeFromThrone, all nine worlds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSeeFromThrone Context triple: [Odin, canSeeFromThrone, all nine worlds]
-
A.
SpeechFromTheThroneLocation
Indicates the location where a formal Speech from the Throne is delivered.
-
B.
acceptedThrone
Indicates that an entity has agreed to assume and take on the role and authority associated with a throne or rulership.
-
C.
hasPhysicalThrone
Indicates that an entity possesses or is associated with a tangible, physical throne as an object.
-
D.
lostThroneTo
Indicates that one entity was previously in possession of a throne or rulership but was defeated or displaced so that another entity took that throne instead.
-
E.
throneName
Indicates the official royal or regnal name adopted by a ruler when they ascend to the throne.
- F. None of above. chosen
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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc21d6d748190980128c1bc5b9621 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
| PDg | Predicate description generation | batch_69abbe4368a88190956bc9ee89c0fd1f |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:48 p.m.