Triple
T15427317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AC Horsens |
E369544
|
entity |
| Predicate | homeCity |
P263
|
FINISHED |
| Object | Horsens |
E369544
|
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: Horsens | Statement: [AC Horsens, homeCity, Horsens]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Horsens Context triple: [AC Horsens, homeCity, Horsens]
-
A.
Horsens
chosen
Horsens is a city in eastern Jutland, Denmark, known historically as a market and industrial town and as the birthplace of explorer Vitus Bering.
-
B.
Herning
Herning is a Danish city in the Central Jutland region known for its trade fairs, conference facilities, and vibrant cultural and sports events.
-
C.
Kolding
Kolding is a historic Danish city in Southern Jutland known for Koldinghus Castle, its fjord-side location, and its role as a regional cultural and educational center.
-
D.
Randers
Randers is a historic market town and one of the largest cities in eastern Jutland, Denmark, known for its old town center and location along the Gudenå River.
-
E.
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.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec31f4881908b26ff7c381d7bc9 |
completed | April 16, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff4546959081909f94449c0028ca3e |
completed | May 9, 2026, 2:31 p.m. |
Created at: April 10, 2026, 3:20 a.m.