Triple
T11616401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thermae Himerenses |
E275519
|
entity |
| Predicate | thermalWatersUsedFor |
P3796
|
FINISHED |
| Object | healing |
—
|
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: healing | Statement: [Thermae Himerenses, thermalWatersUsedFor, healing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thermalWatersUsedFor Context triple: [Thermae Himerenses, thermalWatersUsedFor, healing]
-
A.
hasThermalWaterUse
chosen
Indicates that something makes use of thermal water, typically for purposes such as heating, bathing, energy production, or therapeutic applications.
-
B.
reservoirUse
Indicates the way a reservoir is utilized or the purpose for which its stored water is used.
-
C.
hasThermalBathsSince
Indicates that an entity has had thermal baths available or in operation continuously since a specified point in time.
-
D.
hasNumberOfHotSprings
Indicates the quantity of hot springs associated with a given entity.
-
E.
waterbodyUsedFor
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a04675e08190837a3717242fd0f9 |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.