Triple
T35518950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingslayer |
E1026499
|
entity |
| Predicate | secretMotive |
P34163
|
FINISHED |
| Object | preventing Aerys II from destroying King's Landing |
—
|
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: preventing Aerys II from destroying King's Landing | Statement: [Kingslayer, secretMotive, preventing Aerys II from destroying King's Landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secretMotive Context triple: [Kingslayer, secretMotive, preventing Aerys II from destroying King's Landing]
-
A.
secretRevealed
Indicates that previously hidden or confidential information has been disclosed to one or more parties.
-
B.
reasonForMurder
chosen
Indicates the motive or underlying cause that led someone to commit a murder.
-
C.
revealedSecretOf
Indicates that one entity has disclosed or exposed confidential or previously unknown information belonging to another entity.
-
D.
secretRevealedThrough
Indicates that a secret becomes known or disclosed by means of a specified channel, method, or intermediary.
-
E.
secretes
Indicates that one entity produces and releases a substance from within itself into its surrounding environment or another entity.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:04 p.m.