Triple
T20499019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triesenberg |
E503251
|
entity |
| Predicate | sharesBorderWith |
P224
|
FINISHED |
| Object | Planken |
—
|
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: Planken | Statement: [Triesenberg, sharesBorderWith, Planken]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Planken Context triple: [Triesenberg, sharesBorderWith, Planken]
-
A.
Planken
chosen
Planken is a small mountainous municipality in Liechtenstein known for its rural character and scenic alpine surroundings.
-
B.
Stenen
Stenen is a small village located in the east-central region of the Canadian province of Saskatchewan.
-
C.
Tábua
Tábua is a municipality in central Portugal known for its rural landscapes, traditional villages, and location between the Mondego and Alva rivers.
-
D.
Pločica
Pločica is a village located within the municipality of Kovin in Serbia, known as a small rural settlement in the South Banat District of the Vojvodina region.
-
E.
Blok
Blok is a Russian surname most famously borne by the Symbolist poet Alexander Blok.
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cbff210819089900e9a35911f48 |
completed | April 20, 2026, 9:38 p.m. |
Created at: April 16, 2026, 11:35 a.m.