Triple
T12255259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Henry de Young |
E292083
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | de Young |
E617528
|
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: de Young | Statement: [Michael Henry de Young, familyName, de Young]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: de Young Context triple: [Michael Henry de Young, familyName, de Young]
-
A.
de Young
chosen
de Young is a surname most prominently associated with M. H. de Young, a 19th-century American newspaper publisher and co-founder of the San Francisco Chronicle.
-
B.
Dore
Dore is a suburban village on the southwestern edge of Sheffield, England, known for its affluent residential character and proximity to the Peak District.
-
C.
Dore
The Dore is a river in central France that flows through the Massif Central before joining the Allier.
-
D.
Gugenheim
Gugenheim is a Jewish family surname historically associated with Central and Western Europe, notably linked to several prominent families and individuals.
-
E.
De Jonge
De Jonge is a Dutch surname commonly borne by individuals of Dutch origin and occasionally used in the names of businesses or institutions.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cc9dd5081908880061d52351850 |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60abdc5988190a19104385f54fb06 |
completed | May 2, 2026, 2:31 p.m. |
Created at: April 8, 2026, 9:52 p.m.