Triple
T33737314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aerys II Targaryen |
E864455
|
entity |
| Predicate | swornGuard |
P115487
|
FINISHED |
| Object | Kingsguard |
—
|
NE NERFINISHED |
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: Kingsguard | Statement: [Aerys II Targaryen, swornGuard, Kingsguard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: swornGuard Context triple: [Aerys II Targaryen, swornGuard, Kingsguard]
-
A.
swornDuty
Indicates a formal, binding obligation that one entity has pledged or vowed to uphold toward another entity or cause.
-
B.
swornSword
chosen
Indicates a formal oath of loyalty in which one entity pledges to serve and protect another as their sworn sword.
-
C.
swornInOn
Indicates that an individual formally assumes an office, role, or duty by taking an official oath on a specified date, occasion, or object.
-
D.
swornBrother
Indicates a relationship where two or more individuals have formally pledged brotherhood to each other, typically through an oath signifying deep loyalty and mutual support.
-
E.
swornHouse
Indicates a formal allegiance or oath of loyalty established between one party and a particular house or ruling family.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb54446881909265a17685fa5e4a |
completed | May 3, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:44 a.m.