Triple
T12636131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richards Deep |
E301767
|
entity |
| Predicate | temperatureRangeCelsius |
P99538
|
FINISHED |
| Object | 1–4 |
—
|
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: 1–4 | Statement: [Richards Deep, temperatureRangeCelsius, 1–4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temperatureRangeCelsius Context triple: [Richards Deep, temperatureRangeCelsius, 1–4]
-
A.
humidityRange
Indicates the range of humidity values within which a condition, process, or entity is defined, operates, or remains valid.
-
B.
temperatureRangeDifference
Indicates the difference between two temperature ranges, typically measuring how much one range is higher or lower than another.
-
C.
growthTemperatureRange
Indicates the range of temperatures within which an organism or entity can grow or function effectively.
-
D.
temperatureConditions
chosen
Indicates the specific thermal or weather-related temperature state or range affecting an entity or situation.
-
E.
surfaceTemperatureRange
Indicates the range between the minimum and maximum surface temperatures observed or allowed for an entity.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:16 p.m.