Triple
T38008216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Tears |
E948288
|
entity |
| Predicate | stateAfterEvent |
P195315
|
FINISHED |
| Object | destroyed by fire |
—
|
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: destroyed by fire | Statement: [Temple of Tears, stateAfterEvent, destroyed by fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateAfterEvent Context triple: [Temple of Tears, stateAfterEvent, destroyed by fire]
-
A.
statusAfterEvents
chosen
Indicates the resulting status or condition of an entity after one or more specified events have occurred.
-
B.
legalStatusAfterEvent
Indicates the legal condition or classification an entity has as a result of a specified event or occurrence.
-
C.
settingAfterEvent
Indicates that a particular setting or state occurs subsequent to, and as a result of or in temporal sequence with, a specified event.
-
D.
changesAfterEvents
Indicates that one entity undergoes a change as a consequence of, or following, the occurrence of specified events.
-
E.
maintainedAfterEvent
Indicates that a state, condition, or relationship continues to hold true after a specified event has occurred.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: May 3, 2026, 4:20 p.m.