Triple
T37512619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worldstone |
E932552
|
entity |
| Predicate | destructionConsequence |
P53688
|
FINISHED |
| Object | shattered into many fragments |
—
|
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: shattered into many fragments | Statement: [Worldstone, destructionConsequence, shattered into many fragments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destructionConsequence Context triple: [Worldstone, destructionConsequence, shattered into many fragments]
-
A.
consequenceOfDestruction
chosen
Indicates that one event, state, or condition occurs as a direct result of a prior act of destruction.
-
B.
consequenceOfExplosion
Indicates that something occurs as a direct result or outcome of an explosion.
-
C.
ruptureConsequence
Indicates the resulting state, effect, or outcome that follows from a rupture event.
-
D.
typeOfDestruction
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
-
E.
demolitionImpact
Indicates the effect or consequences that a demolition action has on a target entity or its surrounding environment.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.