Triple
T19594104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atiratra |
E470307
|
entity |
| Predicate | requiresPriestRole |
P34648
|
FINISHED |
| Object | hotṛ |
—
|
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: hotṛ | Statement: [Atiratra, requiresPriestRole, hotṛ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPriestRole Context triple: [Atiratra, requiresPriestRole, hotṛ]
-
A.
hasClergyRequirement
chosen
Indicates that a role, position, or activity requires the person involved to be a member of the clergy or to hold a specific clerical status.
-
B.
requiresOrdinationRank
Indicates that performing or holding a particular role, function, or responsibility is contingent upon having a specified level of ordination rank.
-
C.
isCleric
Indicates that an entity holds the role or status of a cleric, typically serving a religious or spiritual function.
-
D.
hasClericalProtagonist
Indicates that the main character in the work is a member of the clergy or holds a religious office.
-
E.
hasClergyOrder
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640782e2c8190b5baef07a2bdd015 |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.