Triple
T28890344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Throne Room of the Kings |
E732676
|
entity |
| Predicate | eraWithinLegendarium |
P63473
|
FINISHED |
| Object | Third Age |
—
|
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: Third Age | Statement: [Throne Room of the Kings, eraWithinLegendarium, Third Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraWithinLegendarium Context triple: [Throne Room of the Kings, eraWithinLegendarium, Third Age]
-
A.
legendarium
Indicates a relationship where a work, element, or concept belongs to, is part of, or is defined within a particular fictional legendarium or mythic narrative universe.
-
B.
eraCharacter
Indicates that a character is associated with, or belongs to, a particular historical or fictional era.
-
C.
eraEnd
Indicates the point in time or event at which a particular era, period, or phase comes to a close.
-
D.
roleInLegendarium
Indicates that one entity serves a particular narrative or functional role within the fictional mythos or legendarium associated with another entity.
-
E.
eraInCanon
chosen
Indicates that a subject belongs to, occurs within, or is classified as part of a specific era defined in a canon or fictional continuity.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a75dfc88190b919126bcafd64c7 |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:54 a.m.