Triple
T10844571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaun |
E255977
|
entity |
| Predicate | hasAlternativeSpelling |
P457
|
FINISHED |
| Object | Shawn |
E289134
|
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: Shawn | Statement: [Shaun, hasAlternativeSpelling, Shawn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shawn Context triple: [Shaun, hasAlternativeSpelling, Shawn]
-
A.
Shawn
chosen
Shawn is a given name, typically a variant of the name John or Sean, used primarily in English-speaking countries.
-
B.
Shawn Everett
Shawn Everett is a Grammy-winning Canadian audio engineer and record producer known for his innovative, experimental approach to recording and mixing for artists across rock, pop, and alternative music.
-
C.
Shawn Matthews
Shawn Matthews is a senior executive associated with the financial services firm Cantor Fitzgerald.
-
D.
Shayne
Shayne is a given name, typically used as a variant spelling of Shane.
-
E.
Allen Shawn
Allen Shawn is an American composer, pianist, and author known for his concert works, film scores, and reflective non-fiction writing on music and personal experience.
- 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_69e154b2eb08819080a9905dbf378111 |
completed | April 16, 2026, 9:29 p.m. |
Created at: April 8, 2026, 9:19 p.m.