Triple
T19643164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nealey |
E471595
|
entity |
| Predicate | hasAlternativeSpelling |
P457
|
FINISHED |
| Object | Neely |
—
|
NE NERFINISHED |
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: Neely | Statement: [Nealey, hasAlternativeSpelling, Neely]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Neely Context triple: [Nealey, hasAlternativeSpelling, Neely]
-
A.
Neely
chosen
Neely is the surname of Cam Neely, a former professional ice hockey player and current executive best known for his career with the Boston Bruins.
-
B.
Nealy
Nealy is a diminutive or affectionate form of the given name Neal.
-
C.
Neddy
Neddy is Princess Bubblegum’s timid, jelly-like brother who lives beneath the Candy Kingdom in Adventure Time and powers its infrastructure by producing candy juice.
-
D.
Neeley
Neeley is a surname and given name of English origin, used by various notable individuals and families.
-
E.
Neels
Neels is a given name and surname of Dutch or Afrikaans origin, commonly used in South Africa and the Netherlands.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641239ca08190a8bb8854f21ab562 |
completed | April 20, 2026, 3:07 p.m. |
Created at: April 10, 2026, 1:44 p.m.