Triple

T9811992
Position Surface form Disambiguated ID Type / Status
Subject Éomer E238294 entity
Predicate successor P78 FINISHED
Object Elfwine E822688 NE FINISHED

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: Elfwine | Statement: [Éomer, successor, Elfwine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Elfwine
Context triple: [Éomer, successor, Elfwine]
  • A. Elfwine chosen
    Elfwine is a fictional prince of Rohan in J.R.R. Tolkien’s legendarium, known as the son and heir of King Éomer.
  • B. Lewelin
    Lewelin is a variant spelling of the Welsh given name Llewelyn, historically borne by several medieval Welsh princes and nobles.
  • C. Wulfram
    Wulfram is an alternative spelling or variant form of the name Wolfram, which is associated with both a given name and the chemical element tungsten.
  • D. Godric
    Godric is a 1980 historical novel by Frederick Buechner that fictionalizes the life and spiritual journey of the medieval English saint Godric of Finchale.
  • E. Merovech
    Merovech is the semi-legendary Frankish leader regarded as the ancestral founder of the Merovingian royal dynasty in early medieval Gaul.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca84defac48190abc1148804f184c1 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb222ba788190a9085272a3de7852 completed April 2, 2026, 12:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1d5b264c88190bf16c8c32c360878 completed April 5, 2026, 3:23 a.m.
Created at: March 30, 2026, 8:30 p.m.