Triple
T8357290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Excavata |
E196712
|
entity |
| Predicate | typicalCellStructureFeature |
P4603
|
FINISHED |
| Object | one or more flagella |
—
|
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: one or more flagella | Statement: [Excavata, typicalCellStructureFeature, one or more flagella]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCellStructureFeature Context triple: [Excavata, typicalCellStructureFeature, one or more flagella]
-
A.
cellStructure
chosen
Indicates the structural organization, components, and physical arrangement that make up a cell.
-
B.
microscopicStructure
Indicates the detailed arrangement and organization of components at a microscopic scale within an entity.
-
C.
cellType
Indicates the classification relationship that specifies what type of cell an entity is or is associated with.
-
D.
cellularOrganization
Indicates how the components within a biological cell are structured, arranged, and functionally organized in relation to one another.
-
E.
cellularComponent
Indicates the relationship between a biological entity and the specific cellular location or structure in which it is physically present or functions.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb804b57f88190907a4e4e389caf5f |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.