Triple
T24431239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asari |
E616005
|
entity |
| Predicate | majorReligiousFigure |
P43932
|
FINISHED |
| Object | Athame |
—
|
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: Athame | Statement: [Asari, majorReligiousFigure, Athame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorReligiousFigure Context triple: [Asari, majorReligiousFigure, Athame]
-
A.
religiousFigure
chosen
Indicates that one entity is recognized or designated as a religious leader, authority, or sacred person in relation to another entity.
-
B.
headOfReligion
Indicates that one entity serves as the supreme leader or highest authority of a particular religion or religious organization.
-
C.
religiousFigureType
Indicates the specific role or category of a person recognized as a religious figure (e.g., priest, monk, prophet) within a religious context.
-
D.
founderOfReligionAssociated
Indicates that a person is the founder of a religion with which another entity is associated.
-
E.
politicalAndSpiritualLeaderHistorically
Indicates that an entity has historically held both political authority and spiritual or religious leadership over others.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29782a4a0819087cb7ba399371520 |
completed | April 29, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.