Triple
T22939239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson |
E569673
|
entity |
| Predicate | hasEtymologicalRoot |
P5801
|
FINISHED |
| Object | Hugh |
—
|
NE NERFINISHED |
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: Hugh | Statement: [Hudson, hasEtymologicalRoot, Hugh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hugh Context triple: [Hudson, hasEtymologicalRoot, Hugh]
-
A.
Hugh
chosen
Hugh is a masculine given name of Germanic origin, commonly used in English-speaking countries.
-
B.
Henry
Henry is the middle name of William Henry Grenfell, a British politician and sportsman who became 1st Baron Desborough.
-
C.
Henry
Henry is a masculine given name of Germanic origin that has been widely used by European royalty and notable historical figures.
-
D.
Henry
Henry is the given name of Henry Nottidge Moseley, a 19th-century English naturalist and professor known for his work in zoology and participation in the Challenger expedition.
-
E.
Henry
Henry was the given name of Henry Beaufort, 3rd Duke of Somerset, a prominent Lancastrian military commander during the Wars of the Roses in 15th-century England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181378660819083239986c846ec17 |
completed | April 29, 2026, 3:55 a.m. |
Created at: April 17, 2026, 3:45 p.m.