Triple
T530074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2 Chronicles 36 |
E12202
|
entity |
| Predicate | attributesEventTo |
P16468
|
FINISHED |
| Object | wrath of the LORD against His people |
—
|
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: wrath of the LORD against His people | Statement: [2 Chronicles 36, attributesEventTo, wrath of the LORD against His people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attributesEventTo Context triple: [2 Chronicles 36, attributesEventTo, wrath of the LORD against His people]
-
A.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
B.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
C.
basedOnEvent
Indicates that something is derived from, influenced by, or determined in reference to a specific event.
-
D.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
E.
associatedCamp
Indicates a relationship where an entity is linked or connected to a particular camp, typically as its relevant or affiliated camp.
- F. None of above. chosen
Provenance (4 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b257108190a537dffbb9d621b5 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49857e1148190aa782b82675cf0b5 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.