Triple
T34507197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buruista |
E885919
|
entity |
| Predicate | religiousAdvisor |
P2330
|
FINISHED |
| Object | Deceneus |
—
|
NE NERFINISHED |
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: Deceneus | Statement: [Buruista, religiousAdvisor, Deceneus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousAdvisor Context triple: [Buruista, religiousAdvisor, Deceneus]
-
A.
religiousTopicAddressed
Indicates that a subject deals with, discusses, or focuses on a religious theme, issue, or question.
-
B.
religiousTarget
Indicates that an action, policy, or behavior is directed at someone or something specifically because of their religion or religious affiliation.
-
C.
religiousFunction
chosen
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
D.
religiousTextStatus
Indicates the status or role that a text holds within a religious tradition, such as whether it is considered sacred, canonical, apocryphal, or otherwise classified.
-
E.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
Created at: May 1, 2026, 2:01 a.m.