Triple
T917531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Books of Kings |
E19802
|
entity |
| Predicate | canonicalOrderInChristianOldTestament |
P16466
|
FINISHED |
| Object | after 2 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: after 2 Samuel | Statement: [Books of Kings, canonicalOrderInChristianOldTestament, after 2 Samuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalOrderInChristianOldTestament Context triple: [Books of Kings, canonicalOrderInChristianOldTestament, after 2 Samuel]
-
A.
inChristianCanonOrder
chosen
Indicates that the entities are arranged according to the sequence used in the Christian biblical canon.
-
B.
positionInHebrewBible
Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew Bible.
-
C.
bookNumberInNewTestament
Indicates the numerical position a specific book occupies within the sequence of books in the New Testament.
-
D.
chronologicalOrderInGospels
Indicates that the events or elements are arranged in the sequence in which they occur within the Gospel narratives.
-
E.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b2944ff88190a260be5355132ba5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.