Triple
T36721339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manley Hot Springs, Alaska |
E907067
|
entity |
| Predicate | hotSpringsUsage |
P117964
|
FINISHED |
| Object | geothermal heating |
—
|
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: geothermal heating | Statement: [Manley Hot Springs, Alaska, hotSpringsUsage, geothermal heating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hotSpringsUsage Context triple: [Manley Hot Springs, Alaska, hotSpringsUsage, geothermal heating]
-
A.
hotSpringsUsedFor
chosen
Indicates that hot springs serve a particular purpose or are utilized for a specific activity, function, or benefit.
-
B.
hasHotSpring
Indicates that one entity possesses, contains, or is associated with a hot spring.
-
C.
hasNumberOfHotSprings
Indicates the quantity of hot springs associated with a given entity.
-
D.
hasNumberOfMineralSprings
Indicates the relationship that specifies how many mineral springs are associated with a given entity.
-
E.
hasThermalBathsSince
Indicates that an entity has had thermal baths available or in operation continuously since a specified point in time.
- 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.