Triple
T31553323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bleeker, 1863 |
E805061
|
entity |
| Predicate | taxonomicContext |
P174957
|
FINISHED |
| Object | zoological nomenclature |
—
|
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: zoological nomenclature | Statement: [Bleeker, 1863, taxonomicContext, zoological nomenclature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxonomicContext Context triple: [Bleeker, 1863, taxonomicContext, zoological nomenclature]
-
A.
taxonomicUsage
Indicates the way a taxonomic name is applied or used in a particular context, such as in a classification, identification, or reference.
-
B.
taxonomicUncertainty
Indicates uncertainty or doubt about the correct taxonomic identification or classification of an entity in relation to another.
-
C.
taxonomicStatus
Indicates the formal classification status of a taxon within a taxonomic system, such as whether it is accepted, synonymized, provisional, or invalid.
-
D.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
-
E.
taxonomicDomain
Indicates that one entity is the biological taxonomic domain to which the other entity belongs.
- F. None of above. chosen
Provenance (4 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_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: April 30, 2026, 10:12 p.m.