Triple
T12139016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shawn |
E289134
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Shon |
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: Shon | Statement: [Shawn, hasVariant, Shon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shon Context triple: [Shawn, hasVariant, Shon]
-
A.
Shon
chosen
Shon is a given name that functions as an alternative spelling of the more common name Shaun (or Sean).
-
B.
Shinn
Shinn is a surname most notably associated with Everett Shinn, an American realist painter and member of the Ashcan School.
-
C.
Shan
The Shan are a Tai ethnic group primarily inhabiting Myanmar's Shan State, known for their distinct language, Buddhist traditions, and historical Shan principalities.
-
D.
Sharman
Sharman is a surname most notably associated with Helen Sharman, the first British astronaut and the first Western European woman in space.
-
E.
Ryen
Ryen is a residential neighborhood in Oslo, Norway, known for its apartment blocks, local amenities, and good public transport connections.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9158eef48819083bdce283a363414 |
completed | April 10, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f690ae408190966bb4fe8feaa7d2 |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 8, 2026, 9:49 p.m.