Triple
T11466546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corynebacteriales |
E271794
|
entity |
| Predicate | cellEnvelopeFeature |
P38984
|
FINISHED |
| Object | high G+C content in DNA |
—
|
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 G+C content in DNA | Statement: [Corynebacteriales, cellEnvelopeFeature, high G+C content in DNA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellEnvelopeFeature Context triple: [Corynebacteriales, cellEnvelopeFeature, high G+C content in DNA]
-
A.
cellularComponent
Indicates the relationship between a biological entity and the specific cellular location or structure in which it is physically present or functions.
-
B.
cellWallComponent
Indicates that one entity is a molecular or structural component of the cell wall of the other entity.
-
C.
cellType
Indicates the classification relationship that specifies what type of cell an entity is or is associated with.
-
D.
cellStructure
Indicates the structural organization, components, and physical arrangement that make up a cell.
-
E.
genomeCharacteristic
chosen
Indicates that an entity has a specific property, feature, or attribute related to its genome.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f5eb988190b309b8e309f6d1a5 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.