Triple
T35777881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Ems mineral springs |
E1034346
|
entity |
| Predicate | hasSpringName |
P197577
|
FINISHED |
| Object | Kaiserbrunnen |
—
|
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: Kaiserbrunnen | Statement: [Bad Ems mineral springs, hasSpringName, Kaiserbrunnen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpringName Context triple: [Bad Ems mineral springs, hasSpringName, Kaiserbrunnen]
-
A.
hasConfigurationName
Indicates that an entity is associated with or identified by a specific configuration name.
-
B.
hasComponentName
Indicates that an entity includes or is associated with a component identified by a specific name.
-
C.
hasServiceName
Indicates that an entity is associated with or identified by a specific service name.
-
D.
hasRouteName
Indicates that a route, path, or connection is associated with a specific name or label.
-
E.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
| PDg | Predicate description generation | batch_69fe9b013ec481908f89beddb9c4cd4e |
completed | May 9, 2026, 2:25 a.m. |
Created at: May 3, 2026, 4:06 p.m.