Triple
T33111609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aranarth |
E847345
|
entity |
| Predicate | heirlooms |
P20494
|
FINISHED |
| Object | Sceptre of Annúminas |
—
|
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: Sceptre of Annúminas | Statement: [Aranarth, heirlooms, Sceptre of Annúminas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heirlooms Context triple: [Aranarth, heirlooms, Sceptre of Annúminas]
-
A.
traditionalHeir
Indicates that one entity is recognized as the customary or culturally designated inheritor or successor of another entity.
-
B.
hasHeirloom
chosen
Indicates that one entity possesses or is associated with an heirloom originating from another entity.
-
C.
heirOfEstate
Indicates that one entity is legally designated to inherit the estate or property of another entity, typically upon that entity’s death.
-
D.
heritagePrecursor
Indicates that one entity serves as an ancestral or foundational predecessor in the heritage or lineage of another entity.
-
E.
heritageTradition
Indicates a relationship where a cultural practice, belief, or custom is passed down and maintained as part of a group’s inherited traditions.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6eb33648190b26122f53c88d8eb |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.