Triple

T11138461
Position Surface form Disambiguated ID Type / Status
Subject Lancelot (Kingsman) E263475 entity
Predicate inspiredBy P9 FINISHED
Object Sir Lancelot E38009 NE 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: Sir Lancelot | Statement: [Lancelot (Kingsman), inspiredBy, Sir Lancelot]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sir Lancelot
Context triple: [Lancelot (Kingsman), inspiredBy, Sir Lancelot]
  • A. Sir Lancelot chosen
    Sir Lancelot is one of the most famous Knights of the Round Table in Arthurian legend, renowned for his unmatched prowess in battle and his tragic love affair with Queen Guinevere.
  • B. Lancelot
    Lancelot is the codename of Roxy Morton, a skilled Kingsman agent in the "Kingsman" film series.
  • C. Lancelot de Carle
    Lancelot de Carle was a 16th-century French diplomat, poet, and cleric best known for his eyewitness verse account of the fall and execution of Anne Boleyn.
  • D. Sir Galahad
    Sir Galahad is a legendary knight of Arthurian romance renowned for his purity and for achieving the Holy Grail.
  • E. Sir Tristram
    Sir Tristram is a legendary knight of the Round Table in Arthurian romance, renowned for his prowess in battle and his tragic love affair with Iseult.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6aa9c0ba08190bbd19c217489b755 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e85f2ea48190bf1ff63af1d7d236 completed April 9, 2026, 5:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4834b0a0c8190b78ca62badf1f4e4 completed April 19, 2026, 7:24 a.m.
Created at: April 8, 2026, 9:28 p.m.