Triple
T18737175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pré-Saint-Didier |
E458193
|
entity |
| Predicate | hasHotSpringUseSince |
P59136
|
FINISHED |
| Object | Roman times (historically attested use of thermal waters) |
—
|
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: Roman times (historically attested use of thermal waters) | Statement: [Pré-Saint-Didier, hasHotSpringUseSince, Roman times (historically attested use of thermal waters)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHotSpringUseSince Context triple: [Pré-Saint-Didier, hasHotSpringUseSince, Roman times (historically attested use of thermal waters)]
-
A.
hasHotSpring
Indicates that one entity possesses, contains, or is associated with a hot spring.
-
B.
hasThermalBathsSince
chosen
Indicates that an entity has had thermal baths available or in operation continuously since a specified point in time.
-
C.
hasNumberOfHotSprings
Indicates the quantity of hot springs associated with a given entity.
-
D.
hasMineralSprings
Indicates that a place or entity possesses or is characterized by the presence of mineral springs.
-
E.
hasMineralSpringsType
Indicates that an entity is associated with or characterized by a specific type or category of mineral springs.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e57689fa508190ad821d361cba9edf |
completed | April 20, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.