Triple
T23853017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ezekiel 3:12 |
E592223
|
entity |
| Predicate | positionWithinBook |
P66157
|
FINISHED |
| Object | early chapters of Ezekiel |
—
|
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: early chapters of Ezekiel | Statement: [Ezekiel 3:12, positionWithinBook, early chapters of Ezekiel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionWithinBook Context triple: [Ezekiel 3:12, positionWithinBook, early chapters of Ezekiel]
-
A.
hasPositionInBook
chosen
Indicates that an entity occupies a specific position or location within a book.
-
B.
positionInPage
Indicates the specific location or placement of an element within a page’s layout or structure.
-
C.
positionInMushaf
Indicates the specific location or ordering of a text segment within the physical or canonical arrangement of the Mushaf (written Qur’an).
-
D.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
E.
readingLocation
Indicates the place or position where a reading activity occurs or is associated with an 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c9887e5c819089437769acf684c4 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.