Triple

T30098156
Position Surface form Disambiguated ID Type / Status
Subject Sir Boss E764921 entity
Predicate timeDisplacementTo P139932 FINISHED
Object 6th-century Britain 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: 6th-century Britain | Statement: [Sir Boss, timeDisplacementTo, 6th-century Britain]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeDisplacementTo
Context triple: [Sir Boss, timeDisplacementTo, 6th-century Britain]
  • A. timeDisplacedTo chosen
    Indicates that one entity has been moved or transported from its original temporal position to a different point in time relative to another entity or reference time.
  • B. timeEquivalentOf
    Indicates that two temporal entities represent the same point in time or duration, possibly expressed in different formats or units.
  • C. timeShiftProperty
    Indicates a relationship where one property value is derived from another by applying a temporal shift (e.g., offsetting it to an earlier or later point in time).
  • D. timeShiftService
    Indicates that a service is provided with a shifted or delayed time relative to its original or real-time schedule.
  • E. displacementPeriod
    Indicates the time interval over which an entity is moved or shifted from one position or state to another.
  • 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_69f67d92dbdc8190ae3e8f67b979cb5c completed May 2, 2026, 10:41 p.m.
PD Predicate disambiguation batch_69f675ff62c48190a634bbb8896973b9 completed May 2, 2026, 10:09 p.m.
Created at: April 29, 2026, 7:07 p.m.