Triple
T4885995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perseus molecular cloud complex |
E109439
|
entity |
| Predicate | typicalGasTemperature |
P19296
|
FINISHED |
| Object | around 10 Kelvin |
—
|
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: around 10 Kelvin | Statement: [Perseus molecular cloud complex, typicalGasTemperature, around 10 Kelvin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGasTemperature Context triple: [Perseus molecular cloud complex, typicalGasTemperature, around 10 Kelvin]
-
A.
typicalTemperature
chosen
Indicates the usual or characteristic temperature associated with an entity under normal conditions.
-
B.
surfaceTemperature_K
Indicates the temperature of a surface expressed in kelvins.
-
C.
maxSurfaceTemperature
Indicates the highest temperature that the surface of an entity can reach or sustain under specified conditions.
-
D.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
E.
minSurfaceTemperature
Indicates the lowest temperature value observed or allowed on the surface of an object or environment.
- 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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:28 p.m.