Triple
T29019579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nucleariida |
E737414
|
entity |
| Predicate | nucleusNumber |
P166282
|
FINISHED |
| Object | typically uninucleate |
—
|
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: typically uninucleate | Statement: [Nucleariida, nucleusNumber, typically uninucleate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nucleusNumber Context triple: [Nucleariida, nucleusNumber, typically uninucleate]
-
A.
chromosomeNumber
Indicates the specific count of chromosomes associated with an organism, cell, or genetic entity.
-
B.
nucleusType
Indicates the specific kind or classification of nucleus associated with an entity.
-
C.
chromosomeBaseNumber
Indicates the fundamental or characteristic number of distinct chromosomes that typically occur in a complete (haploid) set for a given organism or taxon.
-
D.
hasNuclearRegion
Indicates that an entity possesses or includes a specific nuclear region as a distinct part or component.
-
E.
isNucleusOf
Indicates that one entity functions as the central or most important core component of another entity.
- F. None of above. chosen
Provenance (4 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 9:48 a.m.