Triple
T1181700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thompson |
E25151
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Tompson |
E25151
|
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: Tompson | Statement: [Thompson, hasVariant, Tompson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tompson Context triple: [Thompson, hasVariant, Tompson]
-
A.
Hayes
Hayes is a suburban district in southeast London, England, known for its residential character and green spaces within the London Borough of Bromley.
-
B.
Thompson
chosen
Thompson is a common English-language surname borne by numerous notable individuals across fields such as acting, sports, politics, and science.
-
C.
Lamon
Lamon is an archaeological site notable for inscriptions in the ancient Venetic language.
-
D.
Heinsohn
Heinsohn is a surname most prominently associated with Tom Heinsohn, a Hall of Fame Boston Celtics player, coach, and broadcaster.
-
E.
Tomlinson
Tomlinson is a surname most notably associated with Ray Tomlinson, the American computer programmer credited with inventing networked email and introducing the "@" symbol in email addresses.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd347d4481909e9094463011289d |
completed | March 1, 2026, 10:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac6f21547c81909cf23c454436e839 |
completed | March 7, 2026, 6:32 p.m. |
Created at: March 1, 2026, 7:45 p.m.