Triple
T31552772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swainson, 1839 |
E805048
|
entity |
| Predicate | taxonomicDiscipline |
P119676
|
FINISHED |
| Object | ichthyology |
—
|
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: ichthyology | Statement: [Swainson, 1839, taxonomicDiscipline, ichthyology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxonomicDiscipline Context triple: [Swainson, 1839, taxonomicDiscipline, ichthyology]
-
A.
taxonomicContribution
Indicates a relationship where an entity contributes to or participates in the creation, revision, or clarification of a taxonomic classification or concept.
-
B.
taxonomicUsage
Indicates the way a taxonomic name is applied or used in a particular context, such as in a classification, identification, or reference.
-
C.
fieldOfTaxon
chosen
Indicates the scientific or academic field in which a given taxon is studied or classified.
-
D.
taxonType
Indicates the biological or taxonomic rank/category that characterizes a given taxon.
-
E.
taxonomicStatus
Indicates the formal classification status of a taxon within a taxonomic system, such as whether it is accepted, synonymized, provisional, or invalid.
- 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_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:11 p.m.