Triple
T14638213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yunkai |
E343658
|
entity |
| Predicate | resultOfSiege |
P115162
|
FINISHED |
| Object | slaves freed by Daenerys Targaryen |
—
|
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: slaves freed by Daenerys Targaryen | Statement: [Yunkai, resultOfSiege, slaves freed by Daenerys Targaryen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfSiege Context triple: [Yunkai, resultOfSiege, slaves freed by Daenerys Targaryen]
-
A.
siegeOccurredIn
Indicates that a siege took place within or at the location specified by the related entity.
-
B.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
C.
siegeRelated
Indicates a relationship in which one entity is involved with, associated with, or relevant to a siege or siege-related activities.
-
D.
siegeEndDate
Indicates the date on which a siege concluded or was lifted.
-
E.
sieged
Indicates that one entity has surrounded and blockaded another entity or location, typically to cut off supplies and force surrender.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4aca6448190adf1042dfbfef716 |
completed | April 14, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:26 a.m.