Triple
T37330158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maedhros |
E926720
|
entity |
| Predicate | heldSilmaril |
P187732
|
FINISHED |
| Object | Silmaril of Beren and Lúthien |
—
|
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: Silmaril of Beren and Lúthien | Statement: [Maedhros, heldSilmaril, Silmaril of Beren and Lúthien]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldSilmaril Context triple: [Maedhros, heldSilmaril, Silmaril of Beren and Lúthien]
-
A.
lastHeirOfIsildurToReign
Indicates that the subject is the final reigning ruler who descends from Isildur in the line of succession.
-
B.
ElrondChose
Indicates that Elrond made a deliberate selection or decision regarding a particular option, entity, or course of action.
-
C.
ElrosChose
Indicates that Elros made a deliberate choice or selection among available options.
-
D.
noldorinElement
Indicates a relationship where something is identified as an elemental component or fundamental part within the Noldorin linguistic or conceptual system.
-
E.
Seal of the Hands
Indicates a relationship in which something is formally confirmed, authenticated, or bound through the deliberate action or agreement of specific individuals or parties.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:16 p.m.