Triple
T29008048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mus musculus castaneus |
E736488
|
entity |
| Predicate | hasKaryotype |
P13235
|
FINISHED |
| Object | 40 chromosomes |
—
|
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: 40 chromosomes | Statement: [Mus musculus castaneus, hasKaryotype, 40 chromosomes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKaryotype Context triple: [Mus musculus castaneus, hasKaryotype, 40 chromosomes]
-
A.
guthrieClassification
Indicates a categorization relationship where an entity is assigned a class or type according to the Guthrie classification system.
-
B.
hasGene
Indicates that an entity possesses or contains a specific gene as part of its genetic makeup.
-
C.
hasBalancerChromosomes
Indicates that an organism or genetic sample possesses balancer chromosomes used to maintain specific genetic configurations or prevent recombination.
-
D.
chromosomeNumber
chosen
Indicates the specific count of chromosomes associated with an organism, cell, or genetic entity.
-
E.
isNonChromosomal
Indicates that something does not reside on, derive from, or pertain to a chromosome.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fd9cb788190beb90acc39f381b1 |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:39 a.m.