Triple
T30724983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kra 1 |
E782253
|
entity |
| Predicate | isTypeStrainOf |
P58885
|
FINISHED |
| Object | Thermoproteus tenax |
—
|
NE NERFINISHED |
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: Thermoproteus tenax | Statement: [Kra 1, isTypeStrainOf, Thermoproteus tenax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypeStrainOf Context triple: [Kra 1, isTypeStrainOf, Thermoproteus tenax]
-
A.
targetStrain
Indicates that one entity is the specific strain (e.g., genetic, microbial, or biological variant) that is the focus or objective of another entity’s action, study, or effect.
-
B.
labStrain
chosen
Indicates a relationship where an organism or sample is identified as a specific laboratory strain, typically maintained or derived under controlled lab conditions.
-
C.
isTypeSpeciesOfGenus
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a particular genus.
-
D.
subspeciesOf
Indicates that one taxonomic group is a subspecific rank within, and directly derived from, another species.
-
E.
belongsToSpecies
Indicates that an individual organism is a member of, or classified under, a particular biological species.
- 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_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:36 p.m.