Triple
T18184811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faaborg-Midtfyn Municipality |
E435383
|
entity |
| Predicate | hasSeat |
P3522
|
FINISHED |
| Object | Faaborg |
—
|
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: Faaborg | Statement: [Faaborg-Midtfyn Municipality, hasSeat, Faaborg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Faaborg Context triple: [Faaborg-Midtfyn Municipality, hasSeat, Faaborg]
-
A.
Faaborg
chosen
Faaborg is a historic coastal town on the island of Funen in southern Denmark, known for its well-preserved old town, harbor, and cultural attractions.
-
B.
Nyborg
Nyborg is a historic coastal town and former royal seat in central Denmark, located on the island of Funen.
-
C.
Vordingborg
Vordingborg is a historic coastal town in southern Denmark known for the ruins of Vordingborg Castle and its prominent Goose Tower.
-
D.
Frederikshavn
Frederikshavn is a port town in northern Jutland, Denmark, known for its ferry connections to Norway and Sweden and its maritime industry.
-
E.
Svendborg
Svendborg is a historic coastal town and seaport in southern Denmark known for its maritime heritage and location on the island of Funen.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffdccd881908da772db78b9d081 |
completed | April 19, 2026, 2 p.m. |
Created at: April 10, 2026, 10:31 a.m.