Triple
T4981829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hutchinson |
E111904
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Hutchenson |
E111904
|
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: Hutchenson | Statement: [Hutchinson, hasVariant, Hutchenson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hutchenson Context triple: [Hutchinson, hasVariant, Hutchenson]
-
A.
Hutchinson
chosen
Hutchinson is a common English surname borne by numerous notable individuals across fields such as science, politics, and the arts.
-
B.
Hutchinson
Hutchinson is a long-established British publishing house known for producing a wide range of fiction and non-fiction titles.
-
C.
Hinson
Hinson is a surname most notably associated with former professional basketball player Roy Hinson.
-
D.
Hannan
Hannan is a coastal city in southern Osaka Prefecture, Japan, known for its fishing industry and proximity to Osaka Bay.
-
E.
Tilghman
Tilghman is a masculine given name of English origin that has been borne by various notable American figures, including politicians and military officers.
- 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_69bd441adc208190b70a033a0741d01e |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd725310088190a44b5c02658edc52 |
completed | March 20, 2026, 4:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be8a0f90048190998dad99555891c0 |
completed | March 21, 2026, 12:07 p.m. |
Created at: March 20, 2026, 1:33 p.m.