Triple
T3095603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceboruco |
E64587
|
entity |
| Predicate | hasThermalFeatures |
P39404
|
FINISHED |
| Object | hot 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: hot springs | Statement: [Ceboruco, hasThermalFeatures, hot springs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThermalFeatures Context triple: [Ceboruco, hasThermalFeatures, hot springs]
-
A.
hasThermalActivity
chosen
Indicates that an entity exhibits or is associated with heat-related phenomena such as heating, cooling, or temperature change.
-
B.
usesThermals
Indicates that one entity relies on rising warm air currents (thermals) as a means to gain lift, move, or maintain altitude.
-
C.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
D.
hasThermalWaterUse
Indicates that something makes use of thermal water, typically for purposes such as heating, bathing, energy production, or therapeutic applications.
-
E.
hasHeating
Indicates that an entity is equipped with or provides a heating system or heating capability.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada23b04188190919a69987d2c180f |
completed | March 8, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ad9df06ed88190809f0683122caa5a |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:03 p.m.