Triple
T5171869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shante Broadus |
E116701
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Broadus |
E423790
|
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: Broadus | Statement: [Shante Broadus, familyName, Broadus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Broadus Context triple: [Shante Broadus, familyName, Broadus]
-
A.
Broadus
chosen
Broadus is a surname most notably associated with the family of American rapper Snoop Dogg (Calvin Cordozar Broadus Jr.).
-
B.
Ebersole
Ebersole is a surname most notably associated with American actress and singer Christine Ebersole.
-
C.
Lymon
Lymon is a variant spelling of the given name and surname Lyman, used for people and occasionally fictional characters.
-
D.
Kashmore
Kashmore is a town in Pakistan’s Sindh province that serves as a regional hub near the Guddu Barrage on the Indus River.
-
E.
Considine
Considine is a surname of Irish origin borne by various notable individuals in fields such as politics, entertainment, and sports.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79508610819087abec175da8c847 |
completed | March 20, 2026, 4:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bed9439ec881909021973aa5395e4f |
completed | March 21, 2026, 5:45 p.m. |
Created at: March 20, 2026, 1:45 p.m.