Triple
T3963706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ezekiel 47 |
E85964
|
entity |
| Predicate | locatedInChristianCanon |
P16466
|
FINISHED |
| Object | Prophets |
—
|
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: Prophets | Statement: [Ezekiel 47, locatedInChristianCanon, Prophets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInChristianCanon Context triple: [Ezekiel 47, locatedInChristianCanon, Prophets]
-
A.
inChristianCanonOrder
chosen
Indicates that the entities are arranged according to the sequence used in the Christian biblical canon.
-
B.
canonizedScriptureIn
Indicates that a text or scripture has been formally recognized and included as canonical within a particular religious tradition, community, or collection.
-
C.
canonizedIn
Indicates that an authority formally declared someone to be a saint or holy figure in a specified place or institution.
-
D.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
E.
canonicalStatusInProtestantChurches
Indicates the recognized canonical status or level of acceptance that something holds within Protestant churches.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef8efcf3c81908ccf61d9ce26b0c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:31 p.m.