Triple
T16417106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaun Smith |
E398716
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Shaun |
E915707
|
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: Shaun | Statement: [Shaun Smith, givenName, Shaun]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shaun Context triple: [Shaun Smith, givenName, Shaun]
-
A.
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."
-
B.
Shaun
Shaun is the hapless yet determined protagonist of the British zombie comedy film "Shaun of the Dead," known for his slacker lifestyle and reluctant heroism during a zombie outbreak.
-
C.
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.
-
D.
Shaun
chosen
Shaun is a masculine given name commonly used in English-speaking countries, often considered a variant of Sean or Shawn.
-
E.
Shawn
Shawn is a given name, typically a variant of the name John or Sean, used primarily in English-speaking countries.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32877ff248190886717d3329421a7 |
completed | April 18, 2026, 6:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a003c6ca1bc8190a6c4f675ec8e3a53 |
completed | May 10, 2026, 8:06 a.m. |
Created at: April 10, 2026, 5:09 a.m.