Triple
T14937591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabetta |
E372434
|
entity |
| Predicate | hasHarshEnvironment |
P17982
|
FINISHED |
| Object | extreme cold |
—
|
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: extreme cold | Statement: [Sabetta, hasHarshEnvironment, extreme cold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarshEnvironment Context triple: [Sabetta, hasHarshEnvironment, extreme cold]
-
A.
hasEnvironmentalRisk
Indicates that an entity poses, contributes to, or is associated with potential harm or adverse impact on the environment.
-
B.
hasExtremeWeatherCharacteristic
chosen
Indicates that something possesses a notable or defining feature related to extreme weather conditions.
-
C.
hasRugged
Indicates that something possesses a rough, uneven, or tough physical character or surface.
-
D.
hasEnvironmentalControl
Indicates that one entity regulates, influences, or manages the environmental conditions affecting another entity or area.
-
E.
hasGeneralEnvironment
Indicates that an entity exists or operates within a broad or overall environmental context or setting.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64904d88190b6b4140da8e8199d |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:37 a.m.