Triple
T38615311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesse |
E934597
|
entity |
| Predicate | roleWithinEthnicGroup |
P191294
|
FINISHED |
| Object | prominent Urhobo clan |
—
|
LITERAL 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: prominent Urhobo clan | Statement: [Jesse, roleWithinEthnicGroup, prominent Urhobo clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleWithinEthnicGroup Context triple: [Jesse, roleWithinEthnicGroup, prominent Urhobo clan]
-
A.
mayBelongToEthnicGroup
Indicates that an entity is possibly, but not certainly, a member of a specified ethnic group.
-
B.
commonInEthnicGroup
Indicates that something (such as a trait, condition, or characteristic) occurs with notable frequency within a specified ethnic group.
-
C.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
D.
involvedEthnicGroup
Indicates that a particular ethnic group participates in, is affected by, or is otherwise associated with the referenced event, situation, or entity.
-
E.
supportedByEthnicGroup
Indicates that an entity receives backing, endorsement, or assistance from a particular ethnic group.
- F. None of above. chosen
Provenance (4 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdb0cf6008190b27046b694f84356 |
completed | May 7, 2026, 6:33 p.m. |
Created at: May 3, 2026, 4:32 p.m.