Triple
T21279244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ezekiel 11 |
E524473
|
entity |
| Predicate | declaresJudgmentOn |
P41134
|
FINISHED |
| Object | evil counselors in Jerusalem |
—
|
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: evil counselors in Jerusalem | Statement: [Ezekiel 11, declaresJudgmentOn, evil counselors in Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaresJudgmentOn Context triple: [Ezekiel 11, declaresJudgmentOn, evil counselors in Jerusalem]
-
A.
leadingJudgmentBy
Indicates a relationship where one judgment or legal decision is treated as the primary or authoritative basis guiding or influencing another judgment.
-
B.
judgedOn
Indicates that an entity is evaluated or assessed based on a specified criterion, standard, or aspect.
-
C.
judgmentInvolves
chosen
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
D.
seeksJudgmentFrom
Indicates that one entity actively requests or pursues a formal decision, evaluation, or ruling from another entity.
-
E.
containsJudgmentIn
Indicates that one entity includes or embeds a specific judgment or decision within it.
- 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73659b56c8190af283348378b1cff |
completed | April 21, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 16, 2026, 4:02 p.m.