Triple
T21363635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergheim |
E526848
|
entity |
| Predicate | hasBorderWith |
P224
|
FINISHED |
| Object | Anthering |
—
|
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: Anthering | Statement: [Bergheim, hasBorderWith, Anthering]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anthering Context triple: [Bergheim, hasBorderWith, Anthering]
-
A.
Anthering
chosen
Anthering is a small Austrian municipality in the state of Salzburg, known for its rural character and proximity to the city of Salzburg.
-
B.
Wallanthery
Wallanthery is a small rural locality in New South Wales, Australia, administered as part of the Carrathool Shire Council area.
-
C.
Anserma
Anserma is a municipality and town in the Caldas Department of Colombia, known for its coffee production and location in the Andean region.
-
D.
Antrìm
Antrìm is the Scots name for the town of Antrim in County Antrim, Northern Ireland.
-
E.
Anyer
Anyer is a coastal town in Indonesia known for its beaches on the western tip of Java and as a popular seaside getaway from Jakarta.
- 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_69e0b51d8a308190b09113b3b3f9bc15 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b06cbcb481909ec9014da3b0a18a |
completed | April 22, 2026, 11:26 a.m. |
Created at: April 16, 2026, 5:08 p.m.