Triple
T37568404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urhobo traditional religion |
E934623
|
entity |
| Predicate | definesErivwinAs |
P198799
|
FINISHED |
| Object | spirit world |
—
|
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: spirit world | Statement: [Urhobo traditional religion, definesErivwinAs, spirit world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesErivwinAs Context triple: [Urhobo traditional religion, definesErivwinAs, spirit world]
-
A.
eponymFor
Indicates that one entity gives its name to another entity, which is then named after it.
-
B.
evolutionaryRole
Indicates the function or impact an entity has within an evolutionary process, such as how it contributes to adaptation, selection, or lineage change over time.
-
C.
eraDefinition
Indicates the specific time period or historical era during which something is defined, classified, or considered valid.
-
D.
evolutionaryType
Indicates the kind or category of evolutionary relationship or process that applies between entities.
-
E.
eponymEra
Indicates that a time period or era is named after (or defined by association with) a particular person or entity.
- 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69ff069ddf948190bdfe438953249dd0 |
completed | May 9, 2026, 10:04 a.m. |
Created at: May 3, 2026, 4:17 p.m.