Triple
T33346111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allium |
E853798
|
entity |
| Predicate | hasChromosomeBaseNumber |
P88107
|
FINISHED |
| Object | x=8 |
—
|
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: x=8 | Statement: [Allium, hasChromosomeBaseNumber, x=8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChromosomeBaseNumber Context triple: [Allium, hasChromosomeBaseNumber, x=8]
-
A.
chromosomeBaseNumber
chosen
Indicates the fundamental or characteristic number of distinct chromosomes that typically occur in a complete (haploid) set for a given organism or taxon.
-
B.
chromosomeNumber
Indicates the specific count of chromosomes associated with an organism, cell, or genetic entity.
-
C.
hasChromosomeType
Indicates a relationship where an entity is associated with or characterized by a specific type or category of chromosome.
-
D.
hasBalancerChromosomes
Indicates that an organism or genetic sample possesses balancer chromosomes used to maintain specific genetic configurations or prevent recombination.
-
E.
hasBaseCount
Indicates the number of base units or fundamental components associated with an entity.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: May 1, 2026, 1:34 a.m.