Triple
T35152893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sack of King's Landing |
E1015040
|
entity |
| Predicate | pretextForAttack |
P63220
|
FINISHED |
| Object | offeredSupportToAerysII |
—
|
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: offeredSupportToAerysII | Statement: [Sack of King's Landing, pretextForAttack, offeredSupportToAerysII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pretextForAttack Context triple: [Sack of King's Landing, pretextForAttack, offeredSupportToAerysII]
-
A.
pretext
Indicates that one party uses a stated reason or excuse to conceal their true motive for an action or decision.
-
B.
eventUsedAsPretextFor
chosen
Indicates that one event is cited or leveraged as a justification or excuse for carrying out another action or event.
-
C.
attackContext
Indicates the situational circumstances, conditions, or factors surrounding an attack event or action.
-
D.
plannedAttackWith
Indicates that one entity has prepared or organized an attack using or involving another entity as the means or instrument of that attack.
-
E.
plannedAttack
Indicates that an entity has intentionally prepared and organized an attack against a target.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78cefb12c8190a955da746e14799f |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.