Triple

T2974633
Position Surface form Disambiguated ID Type / Status
Subject Royal Castle in Poznań E80362 entity
Predicate cityPanoramaRole P8652 FINISHED
Object dominant landmark of Poznań Old Town 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: dominant landmark of Poznań Old Town | Statement: [Royal Castle in Poznań, cityPanoramaRole, dominant landmark of Poznań Old Town]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cityPanoramaRole
Context triple: [Royal Castle in Poznań, cityPanoramaRole, dominant landmark of Poznań Old Town]
  • A. hasCityRole
    Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
  • B. urbanRole chosen
    Indicates the function, status, or role that an entity holds within an urban or city context.
  • C. cityPanorama
    Indicates a wide, comprehensive visual view or representation of a cityscape, typically encompassing many of its features in a single scene.
  • D. roleInUrbanPlan
    Indicates the specific function, responsibility, or position an entity holds within an urban planning context or scheme.
  • E. hasMajorCityRole
    Indicates that an entity plays a significant official or functional role in the governance, administration, or key operations of a major city.
  • 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_69ad8b14ffe881908ffed62f9595c867 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad99894bb0819099fa5cc5166c0eeb completed March 8, 2026, 3:45 p.m.
PD Predicate disambiguation batch_69ad96105a708190a9ec4838cbcb1207 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 2:58 p.m.