Triple
T4839030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lag BaOmer |
E108132
|
entity |
| Predicate | mourningCustom |
P59695
|
FINISHED |
| Object | weddings permitted |
—
|
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: weddings permitted | Statement: [Lag BaOmer, mourningCustom, weddings permitted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mourningCustom Context triple: [Lag BaOmer, mourningCustom, weddings permitted]
-
A.
mourningEmphasizedBy
Indicates that one instance of mourning is made more intense, prominent, or noticeable due to the influence or presence of another factor or expression.
-
B.
mourningLevel
Indicates the degree or intensity to which an entity is experiencing or expressing mourning in response to a loss.
-
C.
mourningPeriodBegins
Indicates that the formal period of mourning for a death or loss has started.
-
D.
mourningCause
Indicates that one entity is in a state of mourning specifically because of the other entity, which is the cause or reason for the grief.
-
E.
mourningIntensifiesIn
Indicates that the level or expression of mourning becomes stronger or more intense within a specified context, period, or situation.
- 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_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. |
| PDg | Predicate description generation | batch_69bd6dfff1488190a32bbb615bfab970 |
completed | March 20, 2026, 3:55 p.m. |
Created at: March 20, 2026, 1:25 p.m.