Triple
T28859042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carpediemonas |
E728810
|
entity |
| Predicate | nuclearGenomeOrganization |
P137288
|
FINISHED |
| Object | typical eukaryotic 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: typical eukaryotic chromosomes | Statement: [Carpediemonas, nuclearGenomeOrganization, typical eukaryotic chromosomes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearGenomeOrganization Context triple: [Carpediemonas, nuclearGenomeOrganization, typical eukaryotic chromosomes]
-
A.
geneticMaterialOrganization
Indicates how genetic material is structured, arranged, or organized within or among biological entities.
-
B.
hasGenomeStructure
chosen
Indicates that one entity possesses or is characterized by a specific genome organization or arrangement.
-
C.
cellularOrganization
Indicates how the components within a biological cell are structured, arranged, and functionally organized in relation to one another.
-
D.
hasNuclearRegion
Indicates that an entity possesses or includes a specific nuclear region as a distinct part or component.
-
E.
nucleusType
Indicates the specific kind or classification of nucleus 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:46 a.m.