Triple
T15973593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kristopher Nathan Humphries |
E387382
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Humphries |
E366037
|
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: Humphries | Statement: [Kristopher Nathan Humphries, familyName, Humphries]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Humphries Context triple: [Kristopher Nathan Humphries, familyName, Humphries]
-
A.
Humphries
chosen
Humphries is a surname most famously associated with Australian comedian and satirist Barry Humphries, creator of the character Dame Edna Everage.
-
B.
Humphrys
Humphrys is a surname variant of Humphries, borne by various individuals in English-speaking countries.
-
C.
Humphreys
Humphreys is a small unincorporated community located within Lea County in southeastern New Mexico.
-
D.
Hampson
Hampson is a surname most notably associated with American baritone opera singer Thomas Hampson.
-
E.
Fitzherbert
Fitzherbert is an English surname historically associated with notable figures in British politics, diplomacy, and the aristocracy.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1572b667c8190b28d0556e45422bb |
completed | April 16, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffbe8afa288190838cb35b8a4fcf50 |
completed | May 9, 2026, 11:08 p.m. |
Created at: April 10, 2026, 4:54 a.m.