Triple
T17311165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bassarids |
E420296
|
entity |
| Predicate | ritualCry |
P4193
|
FINISHED |
| Object | evoe |
—
|
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: evoe | Statement: [Bassarids, ritualCry, evoe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualCry Context triple: [Bassarids, ritualCry, evoe]
-
A.
ritualTreatment
Indicates a relationship where an entity performs or undergoes a ritualized act or procedure intended to affect, purify, protect, or transform another entity or condition.
-
B.
usesRitually
Indicates that an entity employs or performs something as part of a ritual or ceremonial practice.
-
C.
ritualEvent
Indicates that an event is a ritual or ceremonial occurrence, typically involving prescribed actions, symbols, or practices performed according to tradition or custom.
-
D.
hasLifecycleRitual
Indicates that an entity is associated with a ritual or ceremonial practice marking a significant stage or transition in its lifecycle.
-
E.
hasRitual
chosen
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399837b08190b7cf74201b3cb013 |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.