Triple
T33164905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bannwaldsee |
E848853
|
entity |
| Predicate | hasMajorNearbyTown |
P3883
|
FINISHED |
| Object | Füssen |
—
|
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: Füssen | Statement: [Bannwaldsee, hasMajorNearbyTown, Füssen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorNearbyTown Context triple: [Bannwaldsee, hasMajorNearbyTown, Füssen]
-
A.
hasNearbyTown
chosen
Indicates that one location has a town situated close to it in geographic proximity.
-
B.
hasNearbyTownType
Indicates that one entity has, in its vicinity, a town of a specified type or classification.
-
C.
hasNearbyMajorCityCountry
Indicates that an entity has a nearby major city located in the specified country.
-
D.
isRemoteFromMajorTowns
Indicates that something is located far away from major towns or urban centers, with limited proximity to them.
-
E.
hasNearestLargerSettlement
Indicates that one settlement is associated with the geographically closest settlement that is larger in size or population.
- F. None of above.
Provenance (3 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00c59b03dc8190870f0dd24603a1ef |
completed | May 10, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_6a00c5178bc88190b2a0e03f38314035 |
completed | May 10, 2026, 5:49 p.m. |
Created at: May 1, 2026, 1:28 a.m.