Triple

T14056801
Position Surface form Disambiguated ID Type / Status
Subject M3 E338239 entity
Predicate serves P98 FINISHED
Object Vesterbro E1082998 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: Vesterbro | Statement: [M3, serves, Vesterbro]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vesterbro
Context triple: [M3, serves, Vesterbro]
  • A. Vesterbro chosen
    Vesterbro is a vibrant, formerly working-class district of Copenhagen known for its trendy bars, restaurants, and cultural scene.
  • B. Nørrebro
    Nørrebro is a vibrant, multicultural district in Copenhagen known for its lively street life, diverse communities, and mix of historic and modern urban culture.
  • C. Østerbro district
    Østerbro district is a central, affluent neighborhood in Copenhagen, Denmark, known for its waterfront areas, green spaces, and elegant residential streets.
  • D. Nørreport
    Nørreport is one of central Copenhagen’s busiest transport hubs, combining metro, S-train, and regional rail services in a major underground station.
  • E. Indre By
    Indre By is the historic city center of Copenhagen, Denmark, known for its cobblestone streets, canals, and many of the capital’s main cultural and architectural landmarks.
  • 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_69d81c67ba6c819091935650dfb3b895 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de3c8e6d008190af8892f34c5cefbd completed April 14, 2026, 1:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd6d756bb48190ae5598e48b281f71 completed May 8, 2026, 4:58 a.m.
Created at: April 9, 2026, 10:20 p.m.