Triple
T31578578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creteuchiloglanis |
E805760
|
entity |
| Predicate | describedInTaxonGroup |
P16820
|
FINISHED |
| Object | sisorid catfishes |
—
|
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: sisorid catfishes | Statement: [Creteuchiloglanis, describedInTaxonGroup, sisorid catfishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedInTaxonGroup Context triple: [Creteuchiloglanis, describedInTaxonGroup, sisorid catfishes]
-
A.
taxonGroup
chosen
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
B.
describedTaxon
Indicates that an entity (such as a publication or description) formally describes or establishes the referenced taxon.
-
C.
hasTaxonomicDescriptions
Indicates that an entity is associated with one or more formal taxonomic descriptions that define or characterize its classification.
-
D.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
-
E.
fieldOfTaxon
Indicates the scientific or academic field in which a given taxon is studied or classified.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 30, 2026, 10:22 p.m.