Triple
T31578412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ituglanis |
E805756
|
entity |
| Predicate | describedInTaxonomicFamily |
P66517
|
FINISHED |
| Object | pencil 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: pencil catfishes | Statement: [Ituglanis, describedInTaxonomicFamily, pencil catfishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedInTaxonomicFamily Context triple: [Ituglanis, describedInTaxonomicFamily, pencil catfishes]
-
A.
describedInFamily
Indicates that an entity is mentioned or characterized within a specific family-related context, such as a family record, lineage, or family description.
-
B.
isTaxonInFamily
chosen
Indicates that a given taxon belongs to, or is classified within, a specified biological family.
-
C.
typeSpeciesOfFamily
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a particular family.
-
D.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
-
E.
describedAsFamilyIn
Indicates that one entity is characterized or referred to as family in the context of another entity or setting.
- 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_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 30, 2026, 10:22 p.m.