Triple

T25966182
Position Surface form Disambiguated ID Type / Status
Subject former Grand Hotel Esplanade E645674 entity
Predicate relocatedComponent P11175 FINISHED
Object Kaisersaal moved about 75 meters 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: Kaisersaal moved about 75 meters | Statement: [former Grand Hotel Esplanade, relocatedComponent, Kaisersaal moved about 75 meters]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relocatedComponent
Context triple: [former Grand Hotel Esplanade, relocatedComponent, Kaisersaal moved about 75 meters]
  • A. relocatedAfter
    Indicates that one entity moved or was transferred to a new location after another specified event or relocation occurred.
  • B. relocated chosen
    Indicates that an entity has moved or been moved from one location or position to another.
  • C. relocatedUsing
    Indicates that an entity was moved or transferred from one place to another by means of a specified method, tool, or transportation mode.
  • D. recoveredComponent
    Indicates that an entity has successfully retrieved or restored a previously lost, damaged, or removed component.
  • E. relocatedDuring
    Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
  • 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_69e77e85efc08190997da7fcf98bd300 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f604c9e74c819090333e44f00abd17 completed May 2, 2026, 2:06 p.m.
PD Predicate disambiguation batch_69f4a10480748190a2e67bd399fc435d completed May 1, 2026, 12:48 p.m.
Created at: April 22, 2026, 8:48 a.m.