Triple
T28694473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oomycota |
E729375
|
entity |
| Predicate | zoosporeFlagellaType |
P31418
|
FINISHED |
| Object | one tinsel-type flagellum |
—
|
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 tinsel-type flagellum | Statement: [Oomycota, zoosporeFlagellaType, one tinsel-type flagellum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoosporeFlagellaType Context triple: [Oomycota, zoosporeFlagellaType, one tinsel-type flagellum]
-
A.
flagella
chosen
Indicates that an entity possesses or is characterized by flagella, typically referring to having one or more whip-like appendages used for movement.
-
B.
sporangiaType
Indicates the type or form of sporangia associated with an organism or structure.
-
C.
ascosporeFeature
Indicates a specific characteristic, quality, or attribute associated with an ascospore in the described relationship or context.
-
D.
gametophyteType
Indicates the specific kind or form of gametophyte (the haploid, gamete-producing life stage) associated with an organism or taxon.
-
E.
hyphalType
Indicates the specific structural or morphological type of hyphae involved in a fungal relationship or process.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 5:38 a.m.