Triple

T4024693
Position Surface form Disambiguated ID Type / Status
Subject Riksbank building, Brunkebergstorg, Stockholm E91362 entity
Predicate locatedInCentralArea P51677 FINISHED
Object central Stockholm 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: central Stockholm | Statement: [Riksbank building, Brunkebergstorg, Stockholm, locatedInCentralArea, central Stockholm]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInCentralArea
Context triple: [Riksbank building, Brunkebergstorg, Stockholm, locatedInCentralArea, central Stockholm]
  • A. isCentralTo
    Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
  • B. isCentralLocalityOf
    Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
  • C. centralLocation
    Indicates that one entity serves as the primary or central place associated with another entity.
  • D. locatedInHubOf chosen
    Indicates that one entity is situated within the central hub or core area associated with another entity.
  • E. locatedNearMetropolitanArea
    Indicates that one entity is situated in close geographic proximity to a metropolitan (urban) area.
  • 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_69aed9618b04819081750d979d2af098 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefacfb23081909a46878adb90ea6c completed March 9, 2026, 4:52 p.m.
PD Predicate disambiguation batch_69aef8fc78ec819092d4dab88d85a141 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:35 p.m.