Triple
T11963460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T. Hee |
E284730
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Thornton |
E716034
|
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: Thornton | Statement: [T. Hee, givenName, Thornton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Thornton Context triple: [T. Hee, givenName, Thornton]
-
A.
Thornton
Thornton is the surname of Terrence LeVarr Thornton, better known as Pusha T, an American rapper and record executive.
-
B.
Thornton
Thornton is a village in Fife, Scotland, known historically for its coal mining and rail junction and now as a small residential community near Glenrothes.
-
C.
Thornton
Thornton is a residential and industrial suburb in the Maitland local government area of New South Wales, Australia.
-
D.
Thornton
chosen
Thornton is a surname of English and Scottish origin borne by numerous notable individuals across fields such as acting, politics, and sports.
-
E.
Thornton
Thornton is a town in Lancashire, England, forming part of the urban area of Thornton-Cleveleys on the Fylde Coast.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037848f481908276716675464464 |
completed | April 10, 2026, 2:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f4594054f08190b28b35f62dfb9198 |
completed | May 1, 2026, 7:41 a.m. |
Created at: April 8, 2026, 9:45 p.m.