Triple
T20318467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Swamp |
E492144
|
entity |
| Predicate | climateFactor |
P30703
|
FINISHED |
| Object | high heat |
—
|
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: high heat | Statement: [The Swamp, climateFactor, high heat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climateFactor Context triple: [The Swamp, climateFactor, high heat]
-
A.
climateDriver
chosen
Indicates a factor or process that significantly influences or drives changes in climate conditions.
-
B.
climateIndicator
Indicates that something serves as a measure or signal of the state, change, or impact of climate-related conditions.
-
C.
climateDependent
Indicates that the existence, behavior, or outcome of something is determined or significantly influenced by climatic conditions.
-
D.
climate
Indicates a relationship where environmental or atmospheric conditions influence, shape, or characterize something (such as a place, system, or process).
-
E.
climateBetween
Indicates that something (such as a location, period, or condition) has a climate that lies within a specified range or intermediate state between two other climatic conditions.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67789d8108190ae2e134f4b0b0be5 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b23a0788190bf1853ef5b81823f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:20 a.m.