Triple
T35481853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Sister |
E1025489
|
entity |
| Predicate | notableKill |
P4646
|
FINISHED |
| Object | Prince Aemon Targaryen |
E398733
|
NE 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: Prince Aemon Targaryen | Statement: [Dark Sister, notableKill, Prince Aemon Targaryen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableKill Context triple: [Dark Sister, notableKill, Prince Aemon Targaryen]
-
A.
notableVictim
Indicates that the subject is a person or entity who is notably recognized as a victim of the object (such as an event, crime, or harmful action).
-
B.
notablePersonKilledThere
Indicates that a notable or famous person was killed at the referenced location.
-
C.
notableAttack
Indicates that an entity carried out, was involved in, or is strongly associated with a particularly significant or well-known attack.
-
D.
notableCommanderKilledInAction
Indicates that a notable military commander associated with an entity was killed in action.
-
E.
killedBy
chosen
Indicates that one entity caused the death of another entity.
- F. None of above.
Provenance (4 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3852dfe5d881909ad98fe0fde1741e |
completed | June 21, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.