Triple
T14707115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackfyre Rebellions |
E345454
|
entity |
| Predicate | firstRebellionOutcome |
P9821
|
FINISHED |
| Object | Targaryen victory |
—
|
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: Targaryen victory | Statement: [Blackfyre Rebellions, firstRebellionOutcome, Targaryen victory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRebellionOutcome Context triple: [Blackfyre Rebellions, firstRebellionOutcome, Targaryen victory]
-
A.
resultOfUprising
chosen
Indicates that something exists or occurs as a consequence or outcome of an uprising or rebellion.
-
B.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
-
C.
firstMajorUprisingEndDate
Indicates the date on which the first major uprising associated with the subject came to an end.
-
D.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
E.
partOfConflictOutcome
Indicates that one entity represents a specific component or aspect of the overall outcome of a conflict involving 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb609965081908f654bcb9eaaa145 |
completed | April 14, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.