Triple
T15088443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leroy P. Steele |
E360345
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Steele |
E296411
|
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: Steele | Statement: [Leroy P. Steele, hasFamilyName, Steele]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Steele Context triple: [Leroy P. Steele, hasFamilyName, Steele]
-
A.
Steele
chosen
Steele is a surname most notably borne by Charles Steele Jr., an American civil rights leader and former president of the Southern Christian Leadership Conference.
-
B.
Steele
Steele is a historic district of the German city of Essen, known for its riverside location along the Ruhr and its blend of residential, commercial, and cultural areas.
-
C.
Steeles
Steeles is a residential and commercial neighbourhood located at the northern edge of Scarborough in Toronto, Ontario, known for its diverse community and suburban character.
-
D.
Blakely
Blakely is a given name and surname of English origin that has become popular as a modern unisex first name.
-
E.
Shriever
Shriever is a surname, a variant spelling of "Shriver," borne by various individuals of English-speaking origin.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00276d1608190bc310d5b86ecd1d5 |
completed | April 15, 2026, 9:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feae1ba4208190b1e8c55668a1b422 |
completed | May 9, 2026, 3:46 a.m. |
Created at: April 10, 2026, 3:04 a.m.