Triple
T1066673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalter |
E23225
|
entity |
| Predicate | traditionalDivision |
P889
|
FINISHED |
| Object | five books |
—
|
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: five books | Statement: [Psalter, traditionalDivision, five books]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalDivision Context triple: [Psalter, traditionalDivision, five books]
-
A.
canonicalDivision
Indicates that one entity is the standard or officially recognized subdivision or partition of another entity.
-
B.
division
chosen
Indicates a relationship where one entity is separated or partitioned into parts, groups, or sections based on some criterion or operation.
-
C.
typeOfDivision
Indicates the specific category or kind of division that characterizes how something is separated, organized, or partitioned.
-
D.
dividedBy
Indicates that one quantity is separated into a specified number of equal parts or groups by another quantity, representing a division relationship between them.
-
E.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
- 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b9e1047481909af1cf8df2a01fff |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b736f1e881909bace735b38c0ade |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.