Triple
T19082729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiferet |
E467069
|
entity |
| Predicate | positionRelativeToChesed |
P134298
|
FINISHED |
| Object | below |
—
|
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: below | Statement: [Tiferet, positionRelativeToChesed, below]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToChesed Context triple: [Tiferet, positionRelativeToChesed, below]
-
A.
positionInTalmud
Indicates the specific location or ordering of a passage, topic, or element within the structured text of the Talmud.
-
B.
positionInAmidah
Indicates the specific location or order of a given element within the sequence of prayers that make up the Amidah.
-
C.
positionRelativeToCaliph
Indicates the spatial or hierarchical position an entity holds in relation to the caliph.
-
D.
positionInHebrewBible
Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew Bible.
-
E.
positionOnJerusalem
Indicates that one entity occupies or is located at a specific position within the area of Jerusalem.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2eab58c8190a987c88d633c92ec |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.