Triple
T19082730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiferet |
E467069
|
entity |
| Predicate | positionRelativeToGevurah |
P134299
|
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, positionRelativeToGevurah, below]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToGevurah Context triple: [Tiferet, positionRelativeToGevurah, below]
-
A.
positionInKutubAlSittah
Indicates the specific placement or ordering of a text or hadith within the canonical six-book collection of Sunni hadith, known as Kutub al-Sittah.
-
B.
positionRelativeToUranium
Indicates the spatial relationship or placement of an entity with respect to a reference point defined by uranium.
-
C.
positionInTalmud
Indicates the specific location or ordering of a passage, topic, or element within the structured text of the Talmud.
-
D.
positionInCosmogony
Indicates the role or place an entity occupies within a culture’s creation or origin narrative of the universe.
-
E.
positionOnQadar
Indicates the stance or doctrinal view an entity holds regarding the concept of divine predestination (Qadar).
- 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.