Triple
T14708258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Sept |
E345481
|
entity |
| Predicate | destroyedUsing |
P49010
|
FINISHED |
| Object | wildfire |
—
|
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: wildfire | Statement: [Great Sept, destroyedUsing, wildfire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destroyedUsing Context triple: [Great Sept, destroyedUsing, wildfire]
-
A.
destroyedFor
Indicates that one entity was ruined, eliminated, or rendered unusable specifically for the benefit, purpose, or objective of another entity.
-
B.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
C.
sufferedDestructionOf
Indicates that one entity experienced damage, ruin, or loss as a result of the destruction of another entity.
-
D.
designedToDestroy
Indicates that one entity was intentionally created or configured for the purpose of damaging, disabling, or annihilating another entity.
-
E.
typeOfDestruction
chosen
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb609965081908f654bcb9eaaa145 |
completed | April 14, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.