Triple
T29725281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chagigah (festival peace offering) |
E752162
|
entity |
| Predicate | broughtOn |
P167813
|
FINISHED |
| Object | Pesach (Passover) |
—
|
NE NERFINISHED |
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: Pesach (Passover) | Statement: [Chagigah (festival peace offering), broughtOn, Pesach (Passover)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broughtOn Context triple: [Chagigah (festival peace offering), broughtOn, Pesach (Passover)]
-
A.
broughtTo
Indicates that one entity caused another entity or object to be transported or accompanied to a particular destination or recipient.
-
B.
broughtBack
Indicates that an entity caused another entity to return to a previous place, state, or condition.
-
C.
airedOn
Indicates that a broadcasted program or episode was shown on a specific channel, platform, or medium.
-
D.
broughtNewsOf
Indicates that one entity conveyed or delivered information or news about another entity or event to a recipient.
-
E.
toldToBring
Indicates that one entity instructed or requested another entity to bring or carry something.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672ff16a08190b8840351bef56f55 |
completed | May 2, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 28, 2026, 7:38 p.m.