Triple
T29618216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pocking |
E754921
|
entity |
| Predicate | locatedInSpaRegion |
P202043
|
FINISHED |
| Object | Bad Füssing spa region |
—
|
LITERAL FINISHED |
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: Bad Füssing spa region | Statement: [Pocking, locatedInSpaRegion, Bad Füssing spa region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInSpaRegion Context triple: [Pocking, locatedInSpaRegion, Bad Füssing spa region]
-
A.
hasSpaTown
Indicates that a place is associated with or contains a town known for its spa or therapeutic bathing facilities.
-
B.
wasSpaTown
Indicates that a place historically functioned as a spa town, known for its therapeutic baths or mineral springs.
-
C.
hasSpaStatusLocation
Indicates that an entity has a specific spa-related status associated with a particular location.
-
D.
hasSpaResort
Indicates that one entity possesses, includes, or is associated with a spa resort as an amenity or feature.
-
E.
hasSpaType
Indicates that an entity is associated with, or classified by, a specific type or category of spa.
- F. None of above. chosen
Provenance (4 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a0049e40d60819081e3899d8d9fca51 |
completed | May 10, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0048c47b548190ad31b2901cc3784a |
completed | May 10, 2026, 8:58 a.m. |
| PDg | Predicate description generation | batch_6a0049e352248190b0a0bb7dfe572c2c |
completed | May 10, 2026, 9:03 a.m. |
Created at: April 28, 2026, 6:33 p.m.