Triple
T30033174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yema |
E763078
|
entity |
| Predicate | usesSacredTextOrLore |
P64294
|
FINISHED |
| Object | Mundhum oral tradition |
—
|
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: Mundhum oral tradition | Statement: [Yema, usesSacredTextOrLore, Mundhum oral tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSacredTextOrLore Context triple: [Yema, usesSacredTextOrLore, Mundhum oral tradition]
-
A.
hasSacredText
Indicates that an entity possesses or is associated with a particular sacred or religious text.
-
B.
hasSacredNarrative
Indicates that one entity possesses, contains, or is associated with a sacred or religiously significant narrative related to another entity.
-
C.
religiousTextsUsed
chosen
Indicates that certain religious texts are employed or referenced in the practice, teaching, or observance associated with an entity.
-
D.
isAssociatedWithReligiousText
Indicates a relationship where an entity is connected or linked in some way to a religious text, such as being based on, derived from, or directly related to it.
-
E.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 29, 2026, 6:50 p.m.