Triple
T598163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bateson, 1885 |
E11432
|
entity |
| Predicate | taxonomicRankDiscussed |
P565
|
FINISHED |
| Object | phylum |
—
|
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: phylum | Statement: [Bateson, 1885, taxonomicRankDiscussed, phylum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxonomicRankDiscussed Context triple: [Bateson, 1885, taxonomicRankDiscussed, phylum]
-
A.
taxonRank
chosen
Indicates the formal hierarchical rank (such as species, genus, family, etc.) that a given taxon occupies within a biological classification system.
-
B.
taxonomicStatus
Indicates the formal classification status of a taxon within a taxonomic system, such as whether it is accepted, synonymized, provisional, or invalid.
-
C.
typeSpecies
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a higher-level group (such as a genus).
-
D.
taxonomicAuthority
Indicates the entity that formally described, named, or classified another entity in a taxonomic context.
-
E.
parentTaxon
Indicates that one taxonomic group is the immediate higher-level (parent) taxon of another taxonomic group.
- 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49dc4f7d08190990f70b9b3af6ce5 |
completed | March 1, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69a49cf59cd0819084e67981cb371e25 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.