Triple
T925154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Ecclesiastes |
E19966
|
entity |
| Predicate | biblicalOrder |
P21149
|
FINISHED |
| Object | one of the Five Megillot |
—
|
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: one of the Five Megillot | Statement: [Book of Ecclesiastes, biblicalOrder, one of the Five Megillot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalOrder Context triple: [Book of Ecclesiastes, biblicalOrder, one of the Five Megillot]
-
A.
inChristianCanonOrder
Indicates that the entities are arranged according to the sequence used in the Christian biblical canon.
-
B.
chronologicalOrderInGospels
Indicates that the events or elements are arranged in the sequence in which they occur within the Gospel narratives.
-
C.
churchOrder
Indicates the hierarchical or organizational structure that defines roles, authority, and governance within a church or religious institution.
-
D.
biblicalName
Indicates that one entity is the name of a person, place, or concept as it appears in the Bible.
-
E.
positionInBible
chosen
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_69a4b2970a4c8190b22cb2fd4706f62b |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.