Triple
T28669226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Man Warner |
E725663
|
entity |
| Predicate | supportsRitual |
P203658
|
FINISHED |
| Object | the lottery |
—
|
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: the lottery | Statement: [Old Man Warner, supportsRitual, the lottery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRitual Context triple: [Old Man Warner, supportsRitual, the lottery]
-
A.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
B.
hasRituals
Indicates that one entity performs, observes, or is associated with specific rituals in relation to another entity or context.
-
C.
usesRitually
Indicates that an entity employs or performs something as part of a ritual or ceremonial practice.
-
D.
hasRitualSetting
Indicates that an entity is associated with a specific ritual context or environment in which it is performed, observed, or situated.
-
E.
hasRitualElements
Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
- F. None of above. chosen
Provenance (4 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a01c21d8bc481909dd9f5a6b89c0a92 |
completed | May 11, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_6a01bff5d1508190895e5bd2c04932b0 |
completed | May 11, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_6a01c21ccebc8190897cb2e9d072e4a7 |
completed | May 11, 2026, 11:48 a.m. |
Created at: April 28, 2026, 5:02 a.m.