Triple
T24001950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaar Perishut |
E594270
|
entity |
| Predicate | commonlyReadIn |
P154828
|
FINISHED |
| Object | Hebrew translation |
—
|
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: Hebrew translation | Statement: [Shaar Perishut, commonlyReadIn, Hebrew translation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyReadIn Context triple: [Shaar Perishut, commonlyReadIn, Hebrew translation]
-
A.
oftenReadDuring
Indicates that something is frequently read or consulted during a particular time, activity, or situation.
-
B.
reading
Indicates that an entity is engaged in the activity of interpreting and understanding written or printed material from another entity or source.
-
C.
alsoReadBy
Indicates that an item (such as a document, article, or book) has been read by another user or entity in addition to the primary one under consideration.
-
D.
readingAid
Indicates that one entity assists or facilitates another entity’s ability to read or engage in reading activities.
-
E.
readingOrganizer
Indicates that an entity is responsible for planning, managing, or coordinating reading-related activities or materials for others.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d4663ca081908317db5c7ce99934 |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:39 p.m.