Triple

T38252862
Position Surface form Disambiguated ID Type / Status
Subject Ser Duncan the Tall E1014099 entity
Predicate swornSwordTo P115487 FINISHED
Object Aegon V Targaryen 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: Aegon V Targaryen | Statement: [Ser Duncan the Tall, swornSwordTo, Aegon V Targaryen]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: swornSwordTo
Context triple: [Ser Duncan the Tall, swornSwordTo, Aegon V Targaryen]
  • A. swornSword chosen
    Indicates a formal oath of loyalty in which one entity pledges to serve and protect another as their sworn sword.
  • B. swornInOn
    Indicates that an individual formally assumes an office, role, or duty by taking an official oath on a specified date, occasion, or object.
  • C. 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.
  • D. swornDuty
    Indicates a formal, binding obligation that one entity has pledged or vowed to uphold toward another entity or cause.
  • E. tinctureOfSword
    Indicates that something is a medicinal or alchemical tincture prepared from, associated with, or derived from a sword.
  • 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_69f76dd7e89c8190b7866bc85aea521b completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcc3321ef081908023590ba70ba0cf completed May 7, 2026, 4:52 p.m.
PD Predicate disambiguation batch_69fcb0fdc6e08190b05e894c59481a0d completed May 7, 2026, 3:34 p.m.
Created at: May 3, 2026, 4:30 p.m.