Triple
T33111842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shards of Narsil |
E847350
|
entity |
| Predicate | re-forgedAs |
P92685
|
FINISHED |
| Object | Andúril, Flame of the West |
—
|
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: Andúril, Flame of the West | Statement: [Shards of Narsil, re-forgedAs, Andúril, Flame of the West]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: re-forgedAs Context triple: [Shards of Narsil, re-forgedAs, Andúril, Flame of the West]
-
A.
reforgedIn
Indicates that an object or material has been melted down or reworked and newly forged within a particular place, context, or process.
-
B.
reforgedFrom
Indicates that something has been newly created or remade by reshaping or reworking a previous object or material.
-
C.
laterReforgedBy
Indicates that an object or work was subsequently remade, reconstructed, or reforged by a specified agent at a later time.
-
D.
isReforgingOf
chosen
Indicates that one object is the result of being remade, reshaped, or reconstructed from another pre-existing object.
-
E.
forgedIn
Indicates that something was created, shaped, or formed within a particular place, context, or process.
- 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.