Triple
T12010726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al HaNissim |
E285896
|
entity |
| Predicate | textualVariation |
P89719
|
FINISHED |
| Object | has minor wording differences among Jewish rites |
—
|
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: has minor wording differences among Jewish rites | Statement: [Al HaNissim, textualVariation, has minor wording differences among Jewish rites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualVariation Context triple: [Al HaNissim, textualVariation, has minor wording differences among Jewish rites]
-
A.
styleVariants
chosen
Indicates that an entity has alternative stylistic forms or versions related to it.
-
B.
textualTransmission
Indicates the transfer or communication of information through written or printed text from one source to another.
-
C.
textBy
Indicates that a given text or written content was authored or produced by a particular entity.
-
D.
languageVariant
Indicates that one language is a variant, dialect, or localized form of another language.
-
E.
textualUniqueness
Indicates that one text is distinct from others in content or expression, without significant duplication or overlap.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d7777481908cd5a001f75e2ee3 |
completed | April 10, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.