Triple
T37422123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christopher Nigel Page |
E929885
|
entity |
| Predicate | hasDescribedTaxonRank |
P200599
|
FINISHED |
| Object | genus |
—
|
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: genus | Statement: [Christopher Nigel Page, hasDescribedTaxonRank, genus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDescribedTaxonRank Context triple: [Christopher Nigel Page, hasDescribedTaxonRank, genus]
-
A.
hasTaxonomicDescriptions
Indicates that an entity is associated with one or more formal taxonomic descriptions that define or characterize its classification.
-
B.
describedByTaxon
Indicates that something is characterized, defined, or otherwise described by a particular taxonomic concept or classification.
-
C.
refersToTaxonRank
Indicates that one entity designates or points to a specific taxonomic rank (such as species, genus, or family) of another biological classification entity.
-
D.
describedTaxon
Indicates that an entity (such as a publication or description) formally describes or establishes the referenced taxon.
-
E.
hasTaxonomicRankAbove
Indicates that one taxonomic rank is hierarchically higher (more inclusive) than another in a classification system.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
| PDg | Predicate description generation | batch_69ff9a24996c8190ba2c5345d317cbdb |
completed | May 9, 2026, 8:33 p.m. |
Created at: May 3, 2026, 4:16 p.m.