Triple
T32654526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torah ark |
E834824
|
entity |
| Predicate | termInHebrew |
P125164
|
FINISHED |
| Object | Aron Kodesh |
—
|
NE NERFINISHED |
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: Aron Kodesh | Statement: [Torah ark, termInHebrew, Aron Kodesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termInHebrew Context triple: [Torah ark, termInHebrew, Aron Kodesh]
-
A.
hebrewMeaning
Indicates that one entity specifies or provides the meaning or translation of another entity in the Hebrew language.
-
B.
correspondsToInHebrew
chosen
Indicates that one entity is the Hebrew-language equivalent or counterpart of another entity.
-
C.
oftenRenderedFromHebrewTerm
Indicates that one term is frequently used as the translation or rendering of a corresponding term originating from Hebrew.
-
D.
titleInHebrew
Indicates that an entity has a specific title expressed in the Hebrew language.
-
E.
openingWordsHebrew
Indicates that the specified words are the opening (initial) words of a text or passage in Hebrew.
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 1:08 a.m.