Triple
T28769920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kusatsu, Gunma |
E726382
|
entity |
| Predicate | hotSpringWaterType |
P55046
|
FINISHED |
| Object | acidic sulfur springs |
—
|
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: acidic sulfur springs | Statement: [Kusatsu, Gunma, hotSpringWaterType, acidic sulfur springs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hotSpringWaterType Context triple: [Kusatsu, Gunma, hotSpringWaterType, acidic sulfur springs]
-
A.
waterType
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
-
B.
hasMineralSpringsType
chosen
Indicates that an entity is associated with or characterized by a specific type or category of mineral springs.
-
C.
hasNumberOfHotSprings
Indicates the quantity of hot springs associated with a given entity.
-
D.
hasHotSpring
Indicates that one entity possesses, contains, or is associated with a hot spring.
-
E.
hotSpringsUsedFor
Indicates that hot springs serve a particular purpose or are utilized for a specific activity, function, or benefit.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:15 a.m.