Triple
T6422442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torah reading |
E127975
|
entity |
| Predicate | scrollScript |
P70786
|
FINISHED |
| Object | Hebrew square script |
—
|
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 square script | Statement: [Torah reading, scrollScript, Hebrew square script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scrollScript Context triple: [Torah reading, scrollScript, Hebrew square script]
-
A.
scriptOnScroll
Indicates that a script is executed or triggered when a scrolling action occurs.
-
B.
scrollPosition
Indicates the current vertical or horizontal offset of a scrollable container relative to its starting position.
-
C.
script
Indicates that an entity is associated with a written text or code (such as a screenplay, program, or written instructions) that defines its content or behavior.
-
D.
scriptDirection
Indicates the direction in which a writing system or script is read or written (e.g., left-to-right, right-to-left, top-to-bottom).
-
E.
scriptAncestor
Indicates that one script is an ancestor of another in a script family or derivation hierarchy, meaning the latter historically descends from or is derived from the former.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0690576c48190b5db5464eacc9de3 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c062d290448190a2183158ef75d129 |
completed | March 22, 2026, 9:44 p.m. |
Created at: March 22, 2026, 4:43 p.m.