Triple
T21552169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domi Richardson |
E531789
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Domi |
—
|
NE NERFINISHED |
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: Domi | Statement: [Domi Richardson, givenName, Domi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Domi Context triple: [Domi Richardson, givenName, Domi]
-
A.
Domi
Domi are an ethnic group, also known as the Dom people, traditionally associated with itinerant lifestyles and found across parts of the Middle East, North Africa, and South Asia.
-
B.
Amar Doman
Amar Doman is a Canadian businessman and entrepreneur best known as the owner of the CFL’s BC Lions and founder of the Futura Corporation.
-
C.
Dominyk
chosen
Dominyk is a given name, typically a modern or stylized variant of the name Dominik.
-
D.
Domo
Domo is a cloud-based business intelligence and data visualization platform that helps organizations integrate, analyze, and share real-time data for decision-making.
-
E.
Dominik
Dominik is a male given name of Slavic origin, commonly used in Central and Eastern Europe.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb59375f481909d9e2b66d18c7c32 |
completed | April 27, 2026, 1:02 a.m. |
Created at: April 16, 2026, 6:29 p.m.