Triple
T16430867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thermal Infrared Sensor |
E399066
|
entity |
| Predicate | enablesDerivationOf |
P75723
|
FINISHED |
| Object | land surface temperature |
—
|
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: land surface temperature | Statement: [Thermal Infrared Sensor, enablesDerivationOf, land surface temperature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesDerivationOf Context triple: [Thermal Infrared Sensor, enablesDerivationOf, land surface temperature]
-
A.
derivationType
Indicates the specific manner or process by which one entity is derived or obtained from another.
-
B.
derivedFrom
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
C.
derivedBy
Indicates that one entity is obtained, produced, or inferred from another through some transformation, process, or reasoning.
-
D.
hasDerivatives
Indicates that one entity is derived, obtained, or developed from another entity.
-
E.
isUsedForDerivatives
chosen
Indicates that something serves as a basis, input, or underlying component for creating or calculating derivatives.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328fe0f488190ac34aa677c980a20 |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.