Triple
T23341588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aakirkeby Church |
E591747
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Aakirkeby |
—
|
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: Aakirkeby | Statement: [Aakirkeby Church, locatedIn, Aakirkeby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aakirkeby Context triple: [Aakirkeby Church, locatedIn, Aakirkeby]
-
A.
Aakirkeby
chosen
Aakirkeby is a small historic town on the Danish island of Bornholm, known for its medieval church and role as a local commercial and cultural center.
-
B.
Kirkeby
Kirkeby is a small settlement located on the Danish island of Bornholm within Bornholm Municipality.
-
C.
Huseby
Huseby is a residential area in Oslo, Norway, known for its green surroundings and location within the Vestre Aker borough.
-
D.
Vällingby
Vällingby is a suburban district in western Stockholm, Sweden, known as a pioneering post-war planned community and modernist housing area.
-
E.
Stureby
Stureby is a residential district in southern Stockholm, Sweden, known for its suburban character and local amenities.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f198334dec819081c432b434eb3ba5 |
completed | April 29, 2026, 5:33 a.m. |
Created at: April 17, 2026, 5:18 p.m.