Triple
T30725024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kra 1 |
E782253
|
entity |
| Predicate | thermostability |
P93629
|
FINISHED |
| Object | high protein thermostability |
—
|
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: high protein thermostability | Statement: [Kra 1, thermostability, high protein thermostability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thermostability Context triple: [Kra 1, thermostability, high protein thermostability]
-
A.
stabilityDefinition
Indicates the formal explanation or criteria that define what is meant by stability in a given context or system.
-
B.
stabilityDescription
Indicates how stable, consistent, or enduring the relationship, condition, or state between the entities is over time.
-
C.
stabilityCharacteristic
chosen
Indicates that one entity specifies a property or feature related to the stability or steadiness of another entity or system.
-
D.
temperatureDependent
Indicates that the existence, intensity, or outcome of a relationship or process varies as a function of temperature.
-
E.
isMetastable
Indicates that a state or configuration is temporarily stable but can transition to a more stable state under small perturbations or over time.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c5c7be08190ad0f9f4f098c0f99 |
completed | May 2, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:36 p.m.