Triple
T11761307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibibio traditional religion |
E279660
|
entity |
| Predicate | hasSourceOfNorms |
P12028
|
FINISHED |
| Object | myths |
—
|
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: myths | Statement: [Ibibio traditional religion, hasSourceOfNorms, myths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceOfNorms Context triple: [Ibibio traditional religion, hasSourceOfNorms, myths]
-
A.
hasNorm
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
-
B.
normativeFor
chosen
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
-
C.
legislationSource
Indicates that one entity serves as the originating authority, basis, or source for a particular piece of legislation or legal rule.
-
D.
hasJudicialPowerSource
Indicates the source or origin from which an entity derives its judicial authority or power.
-
E.
normativelyIncludes
Indicates that one norm or rule encompasses, subsumes, or otherwise includes another within its prescribed scope or requirements.
- F. None of above.
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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a52386708190b744746a2db37495 |
completed | April 10, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69d88a829fe481909cc5431de7d6058e |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.