Triple

T24760588
Position Surface form Disambiguated ID Type / Status
Subject Osdorp E619426 entity
Predicate partOfCitySector P37938 FINISHED
Object western part of Amsterdam 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: western part of Amsterdam | Statement: [Osdorp, partOfCitySector, western part of Amsterdam]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: partOfCitySector
Context triple: [Osdorp, partOfCitySector, western part of Amsterdam]
  • A. inCityDistrict
    Indicates that one entity is located within the boundaries of a specific city district.
  • B. regionOfCity chosen
    Indicates that a specified area or district is a constituent part or subdivision of a particular city.
  • C. targetCityDistrict
    Indicates that one entity is a specific city district that serves as the target or destination in relation to another entity.
  • D. sectorOfGovernedEntity
    Indicates the economic or administrative sector to which a governed entity (such as a jurisdiction or organization under governance) belongs.
  • E. isMunicipalSectorOf
    Indicates that one entity is a municipal-level subdivision, department, or sector that forms part of the organizational structure of another entity (typically a municipality or local government).
  • 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_69e2fabbea94819092ed41348909622f completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f5f6baf2d48190a6a4cd6501be87d2 completed May 2, 2026, 1:06 p.m.
PD Predicate disambiguation batch_69f5afd5baac8190bb8ed576813c8591 completed May 2, 2026, 8:03 a.m.
Created at: April 18, 2026, 4:27 a.m.