Triple
T31553307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bleeker, 1863 |
E805061
|
entity |
| Predicate | refersToTaxonName |
P112215
|
FINISHED |
| Object | Acheilognathidae |
—
|
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: Acheilognathidae | Statement: [Bleeker, 1863, refersToTaxonName, Acheilognathidae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToTaxonName Context triple: [Bleeker, 1863, refersToTaxonName, Acheilognathidae]
-
A.
refersToTaxonRank
Indicates that one entity designates or points to a specific taxonomic rank (such as species, genus, or family) of another biological classification entity.
-
B.
isCitedWithTaxonName
Indicates that a work, statement, or reference is cited together with a specific taxon name in a taxonomic or scientific context.
-
C.
recognizedAsDistinctTaxonBy
Indicates that one entity is formally acknowledged as a separate and distinct taxonomic unit by a specified authority or source.
-
D.
namedTaxon
chosen
Indicates that an entity is identified as, or associated with, a particular taxonomic name.
-
E.
hasEponymousTaxon
Indicates that an entity has a taxonomic group (such as a species or genus) that is named after it.
- 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_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 30, 2026, 10:12 p.m.