Triple

T14645243
Position Surface form Disambiguated ID Type / Status
Subject Sundbyøster E343828 entity
Predicate locatedOn P40 FINISHED
Object Amager E67975 NE 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: Amager | Statement: [Sundbyøster, locatedOn, Amager]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amager
Context triple: [Sundbyøster, locatedOn, Amager]
  • A. Amager Island chosen
    Amager Island is a Danish island in the Øresund Strait that forms a significant part of Copenhagen’s urban area and hosts both residential districts and Copenhagen Airport.
  • B. Valby
    Valby is a district in Copenhagen, Denmark, known as an important local transport and residential area within the city.
  • C. Ennore
    Ennore is a coastal industrial and port suburb in the northern part of Chennai, Tamil Nadu, India.
  • D. Ørestad
    Ørestad is a modern, rapidly developing district on the island of Amager in Copenhagen, known for its contemporary architecture, mixed-use urban planning, and proximity to both the city center and Copenhagen Airport.
  • E. Frederiksberg
    Frederiksberg is an affluent, centrally located municipality in Denmark that forms an enclave within the city of Copenhagen and is known for its parks, cultural institutions, and historic architecture.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d822e1a2cc81908e5bb93cf61ce3cc completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb4ea6d8481908e6331ca173c646b completed April 14, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff36455f788190a63507ecda42b04c completed May 9, 2026, 1:27 p.m.
Created at: April 10, 2026, 1:26 a.m.