Triple
T28859003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trimastix |
E728809
|
entity |
| Predicate | hasCellOrganization |
P29823
|
FINISHED |
| Object | single nucleus |
—
|
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: single nucleus | Statement: [Trimastix, hasCellOrganization, single nucleus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCellOrganization Context triple: [Trimastix, hasCellOrganization, single nucleus]
-
A.
cellularOrganization
chosen
Indicates how the components within a biological cell are structured, arranged, and functionally organized in relation to one another.
-
B.
hadCellStructure
Indicates that an entity possessed a particular cellular organization or arrangement of cells.
-
C.
hasVerticalOrganization
Indicates that one entity is organized in a hierarchical or layered vertical structure relative to another entity or within a system.
-
D.
hasTissueLevelOrganization
Indicates that an entity possesses a structural organization composed of multiple tissues arranged into functional units.
-
E.
hasViewOrganization
Indicates that one entity has the ability or permission to view or access information about an organization.
- 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_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 28, 2026, 6:46 a.m.