Triple
T4839014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lag BaOmer |
E108132
|
entity |
| Predicate | typicalRitual |
P26551
|
FINISHED |
| Object | lighting bonfires |
—
|
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: lighting bonfires | Statement: [Lag BaOmer, typicalRitual, lighting bonfires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRitual Context triple: [Lag BaOmer, typicalRitual, lighting bonfires]
-
A.
partOfRitual
chosen
Indicates that an action, object, or event is included as a component or step within a larger ritual.
-
B.
ritualStructure
Indicates a relationship where an entity is a structure or built feature specifically used for performing rituals or ceremonial practices.
-
C.
ritualCharacteristics
Indicates the defining features, practices, or attributes that characterize a particular ritual.
-
D.
ritualPurpose
Indicates the intended function, goal, or role that a ritual is meant to serve or fulfill.
-
E.
relatedRitual
Indicates that one entity is associated with, connected to, or involved in the performance or context of 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2375a4819098e16acb982c8fab |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.