Triple

T15586607
Position Surface form Disambiguated ID Type / Status
Subject Prinzregentenplatz E374636 entity
Predicate hasBuildingStyleInVicinity P52857 FINISHED
Object historicist architecture 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: historicist architecture | Statement: [Prinzregentenplatz, hasBuildingStyleInVicinity, historicist architecture]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBuildingStyleInVicinity
Context triple: [Prinzregentenplatz, hasBuildingStyleInVicinity, historicist architecture]
  • A. hasBuildingStyleInSurroundings chosen
    Indicates that an entity is surrounded by or located in an area characterized by a particular building style.
  • B. hasNeighboringBuilding
    Indicates that one building is located adjacent to or directly next to another building.
  • C. hasMainBuildingNear
    Indicates that the primary or central building associated with an entity is located in close physical proximity to another specified entity or place.
  • D. hasNearbyPropertyType
    Indicates that one entity has another entity of a specified property type located in close physical proximity to it.
  • E. hasTraditionalHouseStyle
    Indicates that an entity possesses or is characterized by a traditional style of house or residential architecture.
  • 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_69d85ccd575081908909b71a3f3e3a61 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e4900408190aadb48b001db4169 completed April 16, 2026, 2:49 a.m.
PD Predicate disambiguation batch_69deda817e9881909b0c66fc9056f7d5 completed April 15, 2026, 12:23 a.m.
Created at: April 10, 2026, 4:11 a.m.