Triple
T6343892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ta'amei ha-mikra |
E142696
|
entity |
| Predicate | positionRelativeToText |
P23578
|
FINISHED |
| Object | above consonants |
—
|
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: above consonants | Statement: [Ta'amei ha-mikra, positionRelativeToText, above consonants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToText Context triple: [Ta'amei ha-mikra, positionRelativeToText, above consonants]
-
A.
positionedRelativeTo
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
-
B.
relativePosition
chosen
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
C.
positionOnLine
Indicates that one entity occupies a specific location along a defined line or linear path in relation to another.
-
D.
refersToPosition
Indicates that one entity makes reference to, or is associated with, a specific position or location of another entity.
-
E.
positionSpecific
Indicates that something applies only at, or is defined with respect to, a particular position or location within a larger structure or sequence.
- 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0674702d08190806ef0998960b797 |
completed | March 22, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:31 p.m.