Triple
T38560208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mordarski |
E928057
|
entity |
| Predicate | worksOnTaxonOrder |
P99291
|
FINISHED |
| Object | Corynebacteriales |
—
|
NE NERFINISHED |
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: Corynebacteriales | Statement: [Mordarski, worksOnTaxonOrder, Corynebacteriales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksOnTaxonOrder Context triple: [Mordarski, worksOnTaxonOrder, Corynebacteriales]
-
A.
worksOnTaxa
chosen
Indicates that an agent is engaged in research, study, or other work involving specific taxa or taxonomic groups.
-
B.
taxonGroup
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
C.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
-
D.
hasWorkedOnTaxonRank
Indicates that an entity (typically a person or agent) has conducted work, research, or activities specifically related to a taxonomic rank (such as species, genus, family, etc.).
-
E.
typeSpeciesOfOrder
Indicates that a species is the designated type species that defines and represents a particular biological order.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:32 p.m.