Triple
T26296397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loki Patera |
E661430
|
entity |
| Predicate | hasThermalEmission |
P39404
|
FINISHED |
| Object | extremely high |
—
|
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: extremely high | Statement: [Loki Patera, hasThermalEmission, extremely high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThermalEmission Context triple: [Loki Patera, hasThermalEmission, extremely high]
-
A.
hasThermalCharacteristic
Indicates that an entity possesses a specific thermal property or behavior, such as conductivity, capacity, or response to temperature.
-
B.
hasThermalActivity
chosen
Indicates that an entity exhibits or is associated with heat-related phenomena such as heating, cooling, or temperature change.
-
C.
hasThermalResource
Indicates that an entity possesses, provides, or is associated with a source of thermal energy or heat-related capability.
-
D.
emissivityRange
Indicates the range of emissivity values within which an entity’s emission-related property is valid or characterized.
-
E.
hasLowerSurfaceTemperatureThan
Indicates that the surface temperature of one entity is lower than the surface temperature of another 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 10:12 p.m.