Triple
T18458283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 55636 2002 TX300 |
E450960
|
entity |
| Predicate | isDynamicallyCold |
P131722
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [55636 2002 TX300, isDynamicallyCold, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDynamicallyCold Context triple: [55636 2002 TX300, isDynamicallyCold, false]
-
A.
hasColdPhase
Indicates that an entity undergoes or includes a period or stage characterized by low temperature or cold conditions.
-
B.
isColderThan
Indicates that one entity has a lower temperature than another entity.
-
C.
isCryogenic
Indicates that something operates at, is designed for, or involves extremely low (cryogenic) temperatures.
-
D.
isPartOfDynamically
Indicates that one entity is currently a component or member of another entity in a way that can change over time or at runtime.
-
E.
isDynamicallyIsolated
Indicates that an entity operates in a separate, runtime-enforced context or environment such that its state, behavior, or side effects are prevented from directly affecting or being affected by other entities.
- F. None of above. chosen
Provenance (4 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7c18d88190ac17f58111722223 |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:31 a.m.