Triple
T35518974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingslayer |
E1026499
|
entity |
| Predicate | oathBroken |
P165496
|
FINISHED |
| Object | Kingsguard oath to protect the king |
—
|
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: Kingsguard oath to protect the king | Statement: [Kingslayer, oathBroken, Kingsguard oath to protect the king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oathBroken Context triple: [Kingslayer, oathBroken, Kingsguard oath to protect the king]
-
A.
brokeOathTo
chosen
Indicates that one entity violated or failed to honor a sworn promise or commitment made to another entity.
-
B.
penaltyForBreakingOath
Indicates the punishment or negative consequence imposed when an oath is violated.
-
C.
oath
Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
-
D.
oathByStyx
Indicates a relationship where an oath or solemn vow is sworn invoking the River Styx as the binding, unbreakable guarantor of the promise.
-
E.
oathsAbout
Indicates that one entity makes or concerns a formal oath regarding another entity or subject.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.