Triple
T36929838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binding of the Years |
E913447
|
entity |
| Predicate | involvedRitualAction |
P26551
|
FINISHED |
| Object | extinguishing all household fires |
—
|
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: extinguishing all household fires | Statement: [Binding of the Years, involvedRitualAction, extinguishing all household fires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedRitualAction Context triple: [Binding of the Years, involvedRitualAction, extinguishing all household fires]
-
A.
partOfRitual
chosen
Indicates that an action, object, or event is included as a component or step within a larger ritual.
-
B.
initiatesRitual
Indicates that one entity begins or sets in motion a ritual involving one or more other entities.
-
C.
ritualsDirectedAt
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
-
D.
ritualEvent
Indicates that an event is a ritual or ceremonial occurrence, typically involving prescribed actions, symbols, or practices performed according to tradition or custom.
-
E.
ritualOutcome
Indicates the result or consequence produced by performing a particular ritual.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: May 3, 2026, 4:13 p.m.