Triple
T34572314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tevul Yom |
E887656
|
entity |
| Predicate | textualStratum |
P144749
|
FINISHED |
| Object | Mishnah |
—
|
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: Mishnah | Statement: [Tevul Yom, textualStratum, Mishnah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualStratum Context triple: [Tevul Yom, textualStratum, Mishnah]
-
A.
textualStructure
Indicates how parts of a text are organized and related to each other within its overall structure.
-
B.
hasLinguisticStratum
chosen
Indicates a relationship where one element is associated with, or belongs to, a particular layer or level within a linguistic structure or system.
-
C.
textuallySystematizedBy
Indicates that information, concepts, or data are organized, structured, or codified into a systematic textual form by a particular agent or source.
-
D.
textualDivisionOf
Indicates that one text segment functions as a structural subdivision (such as a chapter, section, or paragraph) within another text.
-
E.
textualContinuity
Indicates that one text segment continues, follows, or is sequentially connected to another in the flow of discourse or narrative.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:03 a.m.