Triple
T23853254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torah scroll |
E592228
|
entity |
| Predicate | readWith |
P154196
|
FINISHED |
| Object | yad |
—
|
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: yad | Statement: [Torah scroll, readWith, yad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readWith Context triple: [Torah scroll, readWith, yad]
-
A.
readBy
Indicates that a particular text, document, or content item has been read or consumed by a specific person or agent.
-
B.
readIn
Indicates that an entity reads or studies something within a particular location or context.
-
C.
readsFrom
Indicates that one entity obtains or accesses data, information, or content from another entity as a source.
-
D.
readsInto
Indicates that one entity reads or interprets information from another entity as input or source content.
-
E.
readAfter
Indicates that one entity performs a reading action only after another specified event, action, or reading has occurred.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c98954748190b39e0ac69e5625f9 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:11 p.m.