Triple
T9984267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | people of Madyan |
E196526
|
entity |
| Predicate | destroyedFor |
P91429
|
FINISHED |
| Object | disbelief |
—
|
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: disbelief | Statement: [people of Madyan, destroyedFor, disbelief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destroyedFor Context triple: [people of Madyan, destroyedFor, disbelief]
-
A.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
B.
sufferedDestructionOf
Indicates that one entity experienced damage, ruin, or loss as a result of the destruction of another entity.
-
C.
demolished
Indicates that one entity completely destroyed or razed another entity, typically a structure or object, so that it no longer exists in its previous form.
-
D.
designedToDestroy
Indicates that one entity was intentionally created or configured for the purpose of damaging, disabling, or annihilating another entity.
-
E.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
- 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_69ca82efbce081908179b4b9c65096eb |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb8bdc0388190bbbd4bdc5ac3adec |
completed | April 2, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:49 p.m.