Triple
T31552782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swainson, 1839 |
E805048
|
entity |
| Predicate | taxonHigherGroupDescribed |
P20721
|
FINISHED |
| Object | Cypriniformes |
—
|
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: Cypriniformes | Statement: [Swainson, 1839, taxonHigherGroupDescribed, Cypriniformes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxonHigherGroupDescribed Context triple: [Swainson, 1839, taxonHigherGroupDescribed, Cypriniformes]
-
A.
hasTaxonomicRankAbove
Indicates that one taxonomic rank is hierarchically higher (more inclusive) than another in a classification system.
-
B.
describedTaxon
chosen
Indicates that an entity (such as a publication or description) formally describes or establishes the referenced taxon.
-
C.
parentTaxon
Indicates that one taxonomic group is the immediate higher-level (parent) taxon of another taxonomic group.
-
D.
firstDescribedAsGenusBy
Indicates that one entity was the first to formally describe another entity as a genus in a taxonomic or scientific context.
-
E.
taxonGroup
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:11 p.m.