Triple
T36401834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morton |
E896650
|
entity |
| Predicate | describedTaxonScientificName |
P20721
|
FINISHED |
| Object | Choeropsis liberiensis |
—
|
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: Choeropsis liberiensis | Statement: [Morton, describedTaxonScientificName, Choeropsis liberiensis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedTaxonScientificName Context triple: [Morton, describedTaxonScientificName, Choeropsis liberiensis]
-
A.
describedTaxon
chosen
Indicates that an entity (such as a publication or description) formally describes or establishes the referenced taxon.
-
B.
scientificName
Indicates the formal taxonomic name assigned to an organism according to scientific naming conventions.
-
C.
namedTaxon
Indicates that an entity is identified as, or associated with, a particular taxonomic name.
-
D.
describedByTaxon
Indicates that something is characterized, defined, or otherwise described by a particular taxonomic concept or classification.
-
E.
hasScientificDesignation
Indicates that an entity is associated with a specific formal scientific name or designation used in scientific classification or nomenclature.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 3, 2026, 4:10 p.m.