Triple
T14362834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott McNealy |
E356146
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | McNealy |
E356146
|
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: McNealy | Statement: [Scott McNealy, familyName, McNealy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: McNealy Context triple: [Scott McNealy, familyName, McNealy]
-
A.
McNealy
chosen
McNealy is the surname of Scott McNealy, the American businessman best known as the co-founder and longtime CEO of Sun Microsystems.
-
B.
McNeely
McNeely is a surname of Scottish and Irish origin borne by various notable individuals, including composer and conductor Joel McNeely.
-
C.
Markkula
Markkula is a Finnish surname most notably associated with Mike Markkula, an early investor and executive at Apple Inc.
-
D.
Norvell
Norvell is a surname most prominently associated with American football coach Mike Norvell.
-
E.
Sculley
Sculley is a surname most prominently associated with John Sculley, the former Apple CEO and influential American business executive.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8fabec088190bd8128371b29e958 |
completed | April 14, 2026, 7:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c4aba788190bd5ab8cbc772dcf1 |
completed | May 8, 2026, 2:36 a.m. |
Created at: April 10, 2026, 1:15 a.m.