Triple
T899402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1 Samuel |
E19412
|
entity |
| Predicate | originalCanonOrder |
P6837
|
FINISHED |
| Object | first of the two books of Samuel |
—
|
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: first of the two books of Samuel | Statement: [1 Samuel, originalCanonOrder, first of the two books of Samuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCanonOrder Context triple: [1 Samuel, originalCanonOrder, first of the two books of Samuel]
-
A.
inChristianCanonOrder
Indicates that the entities are arranged according to the sequence used in the Christian biblical canon.
-
B.
originalLensOrder
Indicates that one lens precedes another in the original, intended ordering of lenses.
-
C.
inCanonOf
Indicates that one entity is officially recognized as part of the established canon or authoritative body of works associated with another entity.
-
D.
traditionalOrder
chosen
Indicates that entities are arranged or occur according to a customary, historically established sequence or hierarchy.
-
E.
establishedInOrder
Indicates that one entity was created, founded, or formally set up as a result of, or in accordance with, a specific order, directive, or mandate.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad4162848190aa2787b2fa3e6575 |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa979d408190b17ccfde132ea628 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.