Triple
T33737323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aerys II Targaryen |
E864455
|
entity |
| Predicate | orderedExecutionMethod |
P180908
|
FINISHED |
| Object | burning with wildfire |
—
|
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: burning with wildfire | Statement: [Aerys II Targaryen, orderedExecutionMethod, burning with wildfire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderedExecutionMethod Context triple: [Aerys II Targaryen, orderedExecutionMethod, burning with wildfire]
-
A.
orderedExecutedBy
Indicates that an order or sequence of actions is carried out or fulfilled by a specific agent or executor.
-
B.
outOfOrderExecution
Indicates that actions or operations are carried out in a sequence different from their original or logically expected order.
-
C.
executionOrderedAtRequestOf
Indicates that an execution was carried out according to the wishes or formal request made by a specific party.
-
D.
operationSequence
Indicates that one operation occurs in a specific order relative to another within a defined sequence of actions.
-
E.
executionBy
Indicates that one entity carries out or performs the execution (killing or implementation of a death sentence) of another entity.
- F. None of above. chosen
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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
| PDg | Predicate description generation | batch_69f75788d40c819083bf2567b3091585 |
completed | May 3, 2026, 2:11 p.m. |
Created at: May 1, 2026, 1:44 a.m.