Triple
T28859476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discoba |
E728820
|
entity |
| Predicate | hasNotableMemberTaxon |
P49220
|
FINISHED |
| Object | Trypanosoma |
E727693
|
NE 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: Trypanosoma | Statement: [Discoba, hasNotableMemberTaxon, Trypanosoma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMemberTaxon Context triple: [Discoba, hasNotableMemberTaxon, Trypanosoma]
-
A.
notableMemberTaxon
chosen
Indicates that a taxonomic group has a particular member taxon that is especially notable or representative within that group.
-
B.
hasNotableMember
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
-
C.
hasMemberTaxonRank
Indicates that a group or higher-level taxon includes members classified at a specified taxonomic rank.
-
D.
hasNotableSpecimen
Indicates that an entity possesses or is associated with a specimen that is considered particularly significant, remarkable, or noteworthy.
-
E.
hasImportantTaxonGroup
Indicates that an entity is associated with a taxonomic group considered particularly significant or relevant in a given biological or classification context.
- F. None of above.
Provenance (4 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a262d401a948190b410f0008339c890 |
completed | June 8, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
Created at: April 28, 2026, 6:46 a.m.