Triple
T651929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Ezekiel |
E11362
|
entity |
| Predicate | containsTheme |
P7671
|
FINISHED |
| Object | divine judgment |
—
|
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: divine judgment | Statement: [Book of Ezekiel, containsTheme, divine judgment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsTheme Context triple: [Book of Ezekiel, containsTheme, divine judgment]
-
A.
containsThemeArea
Indicates that one entity includes or encompasses a specific thematic area as part of its scope or content.
-
B.
hasCentralTheme
Indicates that one entity serves as the primary or dominant theme or subject matter of another entity.
-
C.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
D.
notableTheme
chosen
Indicates that a particular theme is prominently featured in, or strongly associated with, an entity such as a work, event, or body of content.
-
E.
hasThemedLand
Indicates that one entity (typically a larger venue or park) includes or is composed of a specific themed land or area as part of its layout or structure.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f35acb08190a3a8248023ce07f9 |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d1001088190aa7ca3c8f2ad0e32 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.