Triple
T29824889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bannik |
E757351
|
entity |
| Predicate | divinationRole |
P27714
|
FINISHED |
| Object | used in marriage divination rituals |
—
|
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: used in marriage divination rituals | Statement: [Bannik, divinationRole, used in marriage divination rituals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divinationRole Context triple: [Bannik, divinationRole, used in marriage divination rituals]
-
A.
divinationMethod
Indicates the method or technique used to perform a divinatory act or practice.
-
B.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
C.
roleInTheProphecy
Indicates that an entity holds a specific function, status, or significance within the context of a particular prophecy.
-
D.
roleInRitual
chosen
Indicates the specific function, position, or responsibility an entity holds within a particular ritual or ceremonial activity.
-
E.
symbolicRoleInProphecy
Indicates that an entity serves as a symbolic figure or sign within a prophecy, representing or foreshadowing specific events, themes, or outcomes.
- 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67596b610819088e85360aafa860c |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:31 p.m.