Triple
T38589258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Frozen Throne |
E932415
|
entity |
| Predicate | resides |
P191456
|
FINISHED |
| Object | Lich King |
—
|
NE NERFINISHED |
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: Lich King | Statement: [The Frozen Throne, resides, Lich King]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resides Context triple: [The Frozen Throne, resides, Lich King]
-
A.
residesUnder
Indicates that one entity lives or is situated beneath another entity in a hierarchical or spatial structure.
-
B.
residence
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
-
C.
hasResidenceOn
Indicates that one entity’s place of residence is located on or along another entity, such as a street, road, or other linear feature.
-
D.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
-
E.
residenceBasedOn
Indicates that an entity’s place of residence is determined or assigned based on a specified criterion, condition, or underlying factor.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:32 p.m.