Triple
T2023902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sephardi-Mizrahi prayer rite |
E44165
|
entity |
| Predicate | hasTextualBase |
P34597
|
FINISHED |
| Object | Sephardi siddur tradition |
—
|
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: Sephardi siddur tradition | Statement: [Sephardi-Mizrahi prayer rite, hasTextualBase, Sephardi siddur tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTextualBase Context triple: [Sephardi-Mizrahi prayer rite, hasTextualBase, Sephardi siddur tradition]
-
A.
hasText
Indicates that an entity is associated with or contains a specific piece of textual content.
-
B.
hasNotableReaderBase
Indicates that an entity is associated with a large, prominent, or otherwise noteworthy group of readers or audience.
-
C.
hasBasicLetters
Indicates that an entity contains or is composed of fundamental alphabetic characters, without additional symbols or diacritics.
-
D.
hasSupportBase
Indicates that one entity serves as the supporting base or foundation upon which another entity rests, is mounted, or is structurally stabilized.
-
E.
haveMajorTextTypes
Indicates that an entity possesses or is associated with specific primary categories or types of texts.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f1728481909ae36e821b9edef2 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb83e7888819096dc40275c77daff |
completed | March 7, 2026, 5:31 a.m. |
Created at: March 4, 2026, 7:38 p.m.