Triple
T33766068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Wenzong of Tang |
E865232
|
entity |
| Predicate | resultOfSweetDewIncident |
P59870
|
FINISHED |
| Object | failure and massacre of officials |
—
|
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: failure and massacre of officials | Statement: [Emperor Wenzong of Tang, resultOfSweetDewIncident, failure and massacre of officials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfSweetDewIncident Context triple: [Emperor Wenzong of Tang, resultOfSweetDewIncident, failure and massacre of officials]
-
A.
resultOfEmergency
Indicates that something occurs or exists as a direct consequence of an emergency situation or event.
-
B.
resultOfFall
Indicates that something exists or occurs as a consequence or outcome of a fall event.
-
C.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
D.
resultOfRaid
Indicates that something is the outcome or consequence produced by a specific raid.
-
E.
resultOfSacrifice
Indicates that something exists or occurs as the outcome or consequence of a sacrificial act.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 1, 2026, 1:45 a.m.