Triple

T18764536
Position Surface form Disambiguated ID Type / Status
Subject Jylland E458858 entity
Predicate containsCity P294 FINISHED
Object Aabenraa 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: Aabenraa | Statement: [Jylland, containsCity, Aabenraa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aabenraa
Context triple: [Jylland, containsCity, Aabenraa]
  • A. Aabenraa chosen
    Aabenraa is a coastal town and seaport in southern Denmark, near the German border, known historically for shipping and trade.
  • B. Holbæk
    Holbæk is a coastal town and municipality in northwestern Zealand, Denmark, known for its harbor on Holbæk Fjord and role as a regional commercial and cultural center.
  • C. Vejle
    Vejle is a Danish city known for its scenic fjord setting, rolling hills, and role as a regional commercial and transportation hub in southeastern Jutland.
  • D. Horsens
    Horsens is a city in eastern Jutland, Denmark, known historically as a market and industrial town and as the birthplace of explorer Vitus Bering.
  • E. Gladsaxe
    Gladsaxe is a municipality in the northern suburbs of Copenhagen, Denmark, known for its residential areas, green spaces, and role as part of the Greater Copenhagen urban region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d395dba0819087568404508590cb completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e58d82297c81909f720e2637cec737 completed April 20, 2026, 2:20 a.m.
Created at: April 10, 2026, 11:52 a.m.