Triple
T37449723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacteria |
E930642
|
entity |
| Predicate | hasTypicalGenomeSizeRange |
P11985
|
FINISHED |
| Object | 0.5–10 megabase pairs |
—
|
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: 0.5–10 megabase pairs | Statement: [Bacteria, hasTypicalGenomeSizeRange, 0.5–10 megabase pairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalGenomeSizeRange Context triple: [Bacteria, hasTypicalGenomeSizeRange, 0.5–10 megabase pairs]
-
A.
genomeSizeRange
chosen
Indicates the range of genome sizes associated with or observed for an entity.
-
B.
genomeSize
Indicates the total amount of genetic material (e.g., in base pairs) contained in an organism’s genome.
-
C.
hasGenomeType
Indicates that an entity possesses or is characterized by a specific type or classification of genome.
-
D.
hasGenomeStructure
Indicates that one entity possesses or is characterized by a specific genome organization or arrangement.
-
E.
estimatedNumberOfGenes
Indicates the approximate count of genes that an entity (such as an organism or genome) is believed to possess.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffde9263248190996f970b6cf6e49d |
completed | May 10, 2026, 1:25 a.m. |
| PD | Predicate disambiguation | batch_69ffdd760f1c8190abc6c0c1cd97ba5f |
completed | May 10, 2026, 1:20 a.m. |
Created at: May 3, 2026, 4:17 p.m.