Triple
T16801273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry Steenbock |
E408359
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Steenbock |
E408359
|
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: Steenbock | Statement: [Harry Steenbock, familyName, Steenbock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Steenbock Context triple: [Harry Steenbock, familyName, Steenbock]
-
A.
Steenbock
chosen
Steenbock is a German-origin surname most notably associated with biochemist Harry Steenbock, known for his pioneering work on vitamin D fortification.
-
B.
Dunnigan
Dunnigan is a small unincorporated community in Yolo County, California, known primarily as a rural agricultural area along Interstate 5.
-
C.
Curdworth
Curdworth is a village in Warwickshire, England, known for its rural character and proximity to Birmingham.
-
D.
Granberry
Granberry is a given name that can function as a surname-style first name, typically of English origin.
-
E.
Bervie
Bervie is a civil parish in Aberdeenshire, Scotland, encompassing the coastal town of Inverbervie and its surrounding area.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2c826808190aa0a5bfcde2e49a8 |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00ab1598dc81909fa5118e739a3291 |
completed | May 10, 2026, 3:58 p.m. |
Created at: April 10, 2026, 5:22 a.m.