Triple
T4240670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayin |
E95403
|
entity |
| Predicate | positionRelativeToSamekh |
P23578
|
FINISHED |
| Object | after Samekh |
—
|
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: after Samekh | Statement: [Ayin, positionRelativeToSamekh, after Samekh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToSamekh Context triple: [Ayin, positionRelativeToSamekh, after Samekh]
-
A.
positionInHebrewBible
Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew Bible.
-
B.
positionInTanakh
Indicates the relative location or ordering of a text or passage within the canonical structure of the Tanakh.
-
C.
positionInHebrewCalendar
Indicates the specific placement or ordering of a time point (such as a date or event) within the structure of the Hebrew calendar.
-
D.
relativePosition
chosen
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
E.
positionInMishnahOrders
Indicates the specific ordinal position that something occupies within the sequence of Mishnah orders.
- 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e87c9d88190a093b1289df5b974 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.