Triple
T11460237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Hartnett |
E271635
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Steve Hartnett |
E271635
|
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: Steve Hartnett | Statement: [Steve Hartnett, name, Steve Hartnett]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Steve Hartnett Context triple: [Steve Hartnett, name, Steve Hartnett]
-
A.
Steve Hartnett
chosen
Steve Hartnett is an individual notable enough to be specifically cited as a bearer of the surname Hartnett.
-
B.
Will Hartnett
Will Hartnett is an American attorney and Republican politician who served as a member of the Texas House of Representatives.
-
C.
Ed Hartnett
Ed Hartnett is an American software developer best known as the creator and primary maintainer of the NetCDF-4 library widely used in scientific computing and data analysis.
-
D.
Tom Hartnett
Tom Hartnett is a notable individual distinguished enough to be recognized as a prominent bearer of the Hartnett surname.
-
E.
Sean Hartnett
Sean Hartnett is a relatively obscure individual whose primary distinguishing feature is sharing the surname Hartnett, with no widely recognized public profile or achievements documented.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f384f08190b1150ed1389dd31a |
completed | April 9, 2026, 10:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef12a7ea2c81909ac2ce2bbe549ebb |
completed | April 27, 2026, 7:39 a.m. |
Created at: April 8, 2026, 9:35 p.m.