Triple
T29852601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DPANN superphylum |
E758101
|
entity |
| Predicate | hasCellMorphology |
P1250
|
FINISHED |
| Object | very small coccoid cells |
—
|
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: very small coccoid cells | Statement: [DPANN superphylum, hasCellMorphology, very small coccoid cells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCellMorphology Context triple: [DPANN superphylum, hasCellMorphology, very small coccoid cells]
-
A.
hasUnusualMorphology
Indicates that an entity possesses structural or anatomical features that deviate significantly from what is typical or expected for its kind.
-
B.
hasMorphologicalType
chosen
Indicates that an entity possesses or is classified by a particular morphological type or structural form.
-
C.
hasContactBinaryMorphology
Indicates that an entity exhibits a binary structure in which two components are in direct physical contact or share a common envelope, forming a contact binary configuration.
-
D.
cellBodyShape
Indicates the characteristic geometric form or outline of a cell’s main body.
-
E.
cellSymmetry
Indicates that two or more cells share the same symmetry properties or exhibit a symmetric spatial or structural relationship.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 29, 2026, 5:44 p.m.