Triple
T18889481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challah |
E462043
|
entity |
| Predicate | hasNumberTradition |
P118449
|
FINISHED |
| Object | two loaves on Shabbat |
—
|
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: two loaves on Shabbat | Statement: [Challah, hasNumberTradition, two loaves on Shabbat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberTradition Context triple: [Challah, hasNumberTradition, two loaves on Shabbat]
-
A.
numberTradition
chosen
Indicates a relationship where a specific number is associated with, or holds significance within, a particular tradition or customary practice.
-
B.
numberInClassicalTradition
Indicates that an entity is associated with a specific number as defined or used within a particular classical tradition (e.g., mythology, religion, or philosophy).
-
C.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
D.
hasSourceTradition
Indicates that something originates from, or is derived within, a particular cultural, religious, intellectual, or historical tradition.
-
E.
hasNumberSystem
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c479f3208190a9d665865c4b630b |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.