Triple

T8677181
Position Surface form Disambiguated ID Type / Status
Subject Guard Hussar Regiment E205944 entity
Predicate garrison P75 FINISHED
Object Slagelse E263377 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: Slagelse | Statement: [Guard Hussar Regiment, garrison, Slagelse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Slagelse
Context triple: [Guard Hussar Regiment, garrison, Slagelse]
  • A. Slagelse chosen
    Slagelse is a town on the island of Zealand in Denmark known for its military presence, historical significance, and role as a regional commercial center.
  • 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. 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.
  • D. 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.
  • E. Næstved
    Næstved is a historic market town and commercial center in southern Denmark, located on the island of Zealand.
  • 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_69ca83529a9c8190b5c075b4f14636ed completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc49f67cdc819092d1ca541c6d22b9 completed March 31, 2026, 10:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69d152541308819098cdca4f3ba9011d completed April 4, 2026, 6:03 p.m.
Created at: March 30, 2026, 6:32 p.m.