Triple
T10844572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaun |
E255977
|
entity |
| Predicate | hasAlternativeSpelling |
P457
|
FINISHED |
| Object | Shaune |
E889550
|
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: Shaune | Statement: [Shaun, hasAlternativeSpelling, Shaune]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shaune Context triple: [Shaun, hasAlternativeSpelling, Shaune]
-
A.
Shauna
Shauna is a feminine given name, commonly considered the female form of Sean and used primarily in English-speaking countries.
-
B.
Shayne
Shayne is a given name, typically used as a variant spelling of Shane.
-
C.
Shon
chosen
Shon is a given name that functions as an alternative spelling of the more common name Shaun (or Sean).
-
D.
Shaun
Shaun is a given name associated with the English actor Sean Bean, known for his roles in film and television such as "The Lord of the Rings" and "Game of Thrones."
-
E.
Shaun
Shaun is one of the principal, allegorical figures in James Joyce’s experimental novel *Finnegans Wake*, often interpreted as a rivalrous brother and foil to Shem within the book’s dreamlike family drama.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d750d0155c81908fb55ba6b45db800 |
completed | April 9, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e2166293808190b7ed1620dfc8a158 |
completed | April 17, 2026, 11:15 a.m. |
Created at: April 8, 2026, 9:19 p.m.