Triple
T19594197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soma sacrifice |
E470309
|
entity |
| Predicate | requiresSpecialist |
P39849
|
FINISHED |
| Object | hotr priest |
—
|
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: hotr priest | Statement: [Soma sacrifice, requiresSpecialist, hotr priest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSpecialist Context triple: [Soma sacrifice, requiresSpecialist, hotr priest]
-
A.
hasSpecialist
chosen
Indicates that one entity is associated with or assigned to a specialist entity that provides expert support, service, or oversight for it.
-
B.
hasSpecialistStatus
Indicates that an entity holds a recognized specialist designation or status in a particular field, role, or context.
-
C.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
D.
hasProfessionalRequirement
Indicates that one entity imposes or specifies a professional qualification, credential, or condition that must be met by another entity.
-
E.
requiresSkill
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
- 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.