Triple

T30244504
Position Surface form Disambiguated ID Type / Status
Subject Spira E769018 entity
Predicate wasImperialCityName P22141 FINISHED
Object true 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: true | Statement: [Spira, wasImperialCityName, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasImperialCityName
Context triple: [Spira, wasImperialCityName, true]
  • A. wasFreeImperialCityOf
    Indicates that an entity formerly held the status of a Free Imperial City within the Holy Roman Empire in relation to another specified entity (typically the empire or its imperial structure).
  • B. wasRoyalCityOf
    Indicates that a city formerly served as the royal or principal city (such as a capital or main seat of power) of a specified kingdom, dynasty, or ruling authority.
  • C. wasCitadelOf
    Indicates that a place previously served as the main fortified stronghold or central defensive structure for another entity.
  • D. wasImportantCityOf chosen
    Indicates that a city held significant importance or prominence within a specified larger political or geographic entity during a given time period.
  • E. hasNumberOfImperialCities
    Indicates the relationship between an entity and the count of imperial cities associated with or contained within it.
  • 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_69f224831dc08190b2e569b987264057 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f68074f0d081909ac1a54ff5f3797d completed May 2, 2026, 10:53 p.m.
PD Predicate disambiguation batch_69f6760216108190bbb708d53a6c2c25 completed May 2, 2026, 10:09 p.m.
Created at: April 29, 2026, 7:39 p.m.