Triple

T30098153
Position Surface form Disambiguated ID Type / Status
Subject Sir Boss E764921 entity
Predicate settingDisplacedTo P16529 FINISHED
Object King Arthur’s court 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: King Arthur’s court | Statement: [Sir Boss, settingDisplacedTo, King Arthur’s court]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: settingDisplacedTo
Context triple: [Sir Boss, settingDisplacedTo, King Arthur’s court]
  • A. intendedDisplacement
    Indicates that an action or event is meant to cause a change in position or location of an entity, regardless of whether that movement actually occurs.
  • B. displacementOption
    Indicates an available way or method by which something or someone can be moved, relocated, or shifted from one position or state to another.
  • C. displacedBy chosen
    Indicates that one entity has been moved, replaced, or forced out of its original position, role, or state by another entity.
  • D. displacementOccurred
    Indicates that an entity has been moved from its original position or location to a different one.
  • E. displacementVariant
    Indicates a relationship where one entity is an alternative or modified form of another that differs specifically in its spatial position or displacement.
  • 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_69f22474e4288190b5f895fe3974aa92 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f72921cf2c8190909bb53f78bcc890 completed May 3, 2026, 10:53 a.m.
PD Predicate disambiguation batch_69f7283d8cec8190b524c144948bc4ec completed May 3, 2026, 10:49 a.m.
Created at: April 29, 2026, 7:07 p.m.