Triple
T4427006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dana |
E95232
|
entity |
| Predicate | nomenclaturalStatus |
P55933
|
FINISHED |
| Object | valid zoological authority name |
—
|
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: valid zoological authority name | Statement: [Dana, nomenclaturalStatus, valid zoological authority name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nomenclaturalStatus Context triple: [Dana, nomenclaturalStatus, valid zoological authority name]
-
A.
taxonomicStatus
Indicates the formal classification status of a taxon within a taxonomic system, such as whether it is accepted, synonymized, provisional, or invalid.
-
B.
nomenclaturalCode
Indicates the formal set of naming rules or code under which an entity’s scientific or taxonomic name is established or governed.
-
C.
namingBasis
Indicates that one entity serves as the reason, source, or criterion for how another entity is named or designated.
-
D.
binomialName
Indicates the formal scientific name assigned to a species, typically composed of its genus and specific epithet.
-
E.
taxonomicAuthority
Indicates the entity that formally described, named, or classified another entity in a taxonomic context.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554fb28081909018eaecc0c5c230 |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3505a87b4819083fbbd58870e520b |
completed | March 12, 2026, 11:46 p.m. |
Created at: March 12, 2026, 11:30 p.m.