Triple
T19481378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unterseen |
E487391
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Habkern |
—
|
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: Habkern | Statement: [Unterseen, borders, Habkern]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Habkern Context triple: [Unterseen, borders, Habkern]
-
A.
Habkern
chosen
Habkern is a small Swiss mountain village and municipality in the canton of Bern, known for its rural alpine landscape and traditional farming character.
-
B.
Eckhard
Eckhard is a masculine given name of German origin, commonly used in German-speaking countries.
-
C.
Reginherus
Reginherus is a Germanic personal name, historically related to and cognate with the legendary Norse name Ragnar.
-
D.
Gundemar
Gundemar was a 7th-century Visigothic king of Hispania and Septimania who ruled briefly before being succeeded by Sisebut.
-
E.
Thankmar
Thankmar was a 10th-century German nobleman and the eldest son of King Henry the Fowler, whose disputed legitimacy led to his rebellion against his half-brother Otto I.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e634393b8081909f5e4c38b2f1a9b7 |
completed | April 20, 2026, 2:12 p.m. |
Created at: April 10, 2026, 1:39 p.m.