Triple
T2828089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinkaku-ji |
E54970
|
entity |
| Predicate | arsonPerpetrator |
P698
|
FINISHED |
| Object | young monk |
—
|
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: young monk | Statement: [Kinkaku-ji, arsonPerpetrator, young monk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arsonPerpetrator Context triple: [Kinkaku-ji, arsonPerpetrator, young monk]
-
A.
murderVictimOf
Indicates that one entity is the person who was killed by another entity in an act of murder.
-
B.
allegedToHaveKilled
Indicates that one entity is claimed or accused, but not proven, to have killed another entity.
-
C.
suspectedPerpetrator
Indicates that an entity is believed or alleged to be the person responsible for committing a particular harmful or illegal act.
-
D.
perpetratedBy
chosen
Indicates that an action, event, or wrongdoing was carried out or caused by a particular agent or entity.
-
E.
reasonForMurder
Indicates the motive or underlying cause that led someone to commit a murder.
- 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde95d8148190bcae8b0659a5c116 |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.