Triple
T13937151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yvain |
E335147
|
entity |
| Predicate | alternativeName |
P39
|
FINISHED |
| Object | Ewain |
E262005
|
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: Ewain | Statement: [Yvain, alternativeName, Ewain]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ewain Context triple: [Yvain, alternativeName, Ewain]
-
A.
Gwindor
Gwindor is an Elf of the First Age in J.R.R. Tolkien’s legendarium, known for his tragic capture in Angband and his role in aiding Túrin Turambar.
-
B.
Hilduin
Hilduin was a medieval nobleman known primarily as a descendant of the influential Ottonian dynasty through his mother, Gerberga of Saxony.
-
C.
Alwyn
Alwyn is a surname most notably associated with the English composer and conductor William Alwyn.
-
D.
Owain
chosen
Owain is a given name of Welsh origin, traditionally borne by several figures in Welsh mythology and medieval literature.
-
E.
Camlan
Camlan is the legendary battlefield in Arthurian tradition where King Arthur is said to have fought his final, fatal conflict.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf42878819085146670d7b92605 |
completed | April 14, 2026, 12:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7ce880a98819086ae25d3408bc723 |
completed | May 3, 2026, 10:39 p.m. |
Created at: April 9, 2026, 10:17 p.m.