Triple
T2980951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resh |
E80507
|
entity |
| Predicate | isRadicalInHebrewDictionaryOrdering |
P44429
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Resh, isRadicalInHebrewDictionaryOrdering, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRadicalInHebrewDictionaryOrdering Context triple: [Resh, isRadicalInHebrewDictionaryOrdering, true]
-
A.
hasNameInHebrew
Indicates that an entity is associated with a specific name expressed in the Hebrew language.
-
B.
positionInHebrewCalendar
Indicates the specific placement or ordering of a time point (such as a date or event) within the structure of the Hebrew calendar.
-
C.
hasRomanizationOf
Indicates that one entity is a romanized representation (written in the Latin alphabet) of the other entity’s original script form.
-
D.
positionInHebrewBible
Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew Bible.
-
E.
hasCyrillicAlphabetForm
Indicates that an entity has a corresponding representation or form written in the Cyrillic alphabet.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999e91788190a2d430dd0600a660 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:58 p.m.