Triple
T33130330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johann Jakob Heckel |
E847841
|
entity |
| Predicate | honouredInTaxonName |
P74962
|
FINISHED |
| Object | Symphysodon discus heckel |
—
|
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: Symphysodon discus heckel | Statement: [Johann Jakob Heckel, honouredInTaxonName, Symphysodon discus heckel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honouredInTaxonName Context triple: [Johann Jakob Heckel, honouredInTaxonName, Symphysodon discus heckel]
-
A.
honouredInTaxon
chosen
Indicates that an organism or taxonomic group is named in honor of a particular person, entity, or concept.
-
B.
hasHonorificNameInTaxon
Indicates that an entity has an honorific (commemorative) name specifically within the context of a given taxonomic classification.
-
C.
notableMemberTaxon
Indicates that a taxonomic group has a particular member taxon that is especially notable or representative within that group.
-
D.
namedTaxon
Indicates that an entity is identified as, or associated with, a particular taxonomic name.
-
E.
alsoHonoredAs
Indicates that an entity is additionally recognized or celebrated under another title, role, or form of honor beyond its primary designation.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:27 a.m.