Triple
T34813666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timi of Ede |
E1003566
|
entity |
| Predicate | associatedWithEthnicSubgroup |
P1969
|
FINISHED |
| Object | Ede people |
E510162
|
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: Ede people | Statement: [Timi of Ede, associatedWithEthnicSubgroup, Ede people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithEthnicSubgroup Context triple: [Timi of Ede, associatedWithEthnicSubgroup, Ede people]
-
A.
linkedToEthnicIdentity
Indicates a relationship where something is associated or connected with a particular ethnic identity.
-
B.
relatedEthnicGroup
chosen
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
-
C.
mayBelongToEthnicGroup
Indicates that an entity is possibly, but not certainly, a member of a specified ethnic group.
-
D.
containedEthnicGroup
Indicates that one entity (typically a larger group, region, or population) includes or encompasses a particular ethnic group within it.
-
E.
supportedByEthnicGroup
Indicates that an entity receives backing, endorsement, or assistance from a particular ethnic group.
- F. None of above.
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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a376fb3568081908c8ce4c8e76747e4 |
completed | June 21, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.