Triple
T19863793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Scrolls |
E477334
|
entity |
| Predicate | scripturalDivision |
P37110
|
FINISHED |
| Object | Writings |
—
|
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: Writings | Statement: [Five Scrolls, scripturalDivision, Writings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scripturalDivision Context triple: [Five Scrolls, scripturalDivision, Writings]
-
A.
scripturalSection
chosen
Indicates a relationship where one text or passage is a specific section or subdivision within a larger scriptural work.
-
B.
scriptureType
Indicates the classification or category of a scripture in relation to its type or genre.
-
C.
scripturalCorpus
Indicates that one entity is a body of scriptural or sacred texts associated with, or serving as the canonical writings for, another entity.
-
D.
scripturalNumberingSystem
Indicates a relationship where a particular numbering system is used to organize, reference, or index passages within a scriptural text.
-
E.
scripturalChapters
Indicates that one entity is composed of, contains, or is divided into the specified scriptural chapters.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6589d55a88190af7d4e12c4b07739 |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.