Triple
T34424114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Seeds |
E883623
|
entity |
| Predicate | canonicalDivisionOf |
P6848
|
FINISHED |
| Object | Oral Torah |
—
|
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: Oral Torah | Statement: [Order of Seeds, canonicalDivisionOf, Oral Torah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalDivisionOf Context triple: [Order of Seeds, canonicalDivisionOf, Oral Torah]
-
A.
canonicalDivision
chosen
Indicates that one entity is the standard or officially recognized subdivision or partition of another entity.
-
B.
formalizedDivisionOf
Indicates a relationship where one entity is officially and explicitly divided into distinct parts or sub-entities according to a formal rule, structure, or agreement.
-
C.
containsDivision
Indicates that one entity includes or encompasses a subdivision or internal division of another entity.
-
D.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
E.
typicalDivision
Indicates that one entity is a standard or characteristic subdivision or component of another entity.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2 a.m.