Triple

T25906154
Position Surface form Disambiguated ID Type / Status
Subject Legionowo E652755 entity
Predicate isSuburbanSatelliteOf P15376 FINISHED
Object Warsaw 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: Warsaw | Statement: [Legionowo, isSuburbanSatelliteOf, Warsaw]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isSuburbanSatelliteOf
Context triple: [Legionowo, isSuburbanSatelliteOf, Warsaw]
  • A. isSuburbanCityOf chosen
    Indicates that one city is a suburban municipality that is part of, or closely associated with, a larger primary city or metropolitan area.
  • B. isUrbanSatelliteOf
    Indicates that a smaller urban area or city functions as a dependent or closely linked satellite to a larger primary city or metropolitan center.
  • C. containsSuburbanAreaOf
    Indicates that one geographic region includes within its boundaries a suburban area belonging to or associated with another region.
  • D. isSuburbanNeighborhoodOf
    Indicates that one area is a residential neighborhood located within or characteristic of the suburbs of another, typically larger, urban area.
  • E. isSuburbanArea
    Indicates that a location is characterized as a suburban area, typically lying between urban and rural regions and exhibiting suburban development patterns.
  • 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_69e7ab3d3f8481909bc53ed64c06af33 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f627aedf548190bc9f53c8a2d67b50 completed May 2, 2026, 4:34 p.m.
PD Predicate disambiguation batch_69f623a4e1048190bbb8dd1253fdcee9 completed May 2, 2026, 4:17 p.m.
Created at: April 22, 2026, 8:27 a.m.