Triple
T29618236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pocking |
E754921
|
entity |
| Predicate | nearSpaTown |
P130405
|
FINISHED |
| Object | Bad Füssing |
—
|
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: Bad Füssing | Statement: [Pocking, nearSpaTown, Bad Füssing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearSpaTown Context triple: [Pocking, nearSpaTown, Bad Füssing]
-
A.
nearOnsenTown
chosen
Indicates that one entity is located close to a town that has or is known for hot spring facilities.
-
B.
hasSpaTown
Indicates that a place is associated with or contains a town known for its spa or therapeutic bathing facilities.
-
C.
wasSpaTown
Indicates that a place historically functioned as a spa town, known for its therapeutic baths or mineral springs.
-
D.
nearbyResortArea
Indicates that a resort area is located close to or within a short distance of a specified place or entity.
-
E.
nearbyResortSection
Indicates that one resort section is located close to another resort section in physical proximity.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e227eec8190a5e5a8de8359875b |
completed | May 2, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:33 p.m.