Triple
T25209415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | (Bong.) Carrière |
E631640
|
entity |
| Predicate | associatedWithTaxonRank |
P11700
|
FINISHED |
| Object | species |
—
|
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: species | Statement: [(Bong.) Carrière, associatedWithTaxonRank, species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTaxonRank Context triple: [(Bong.) Carrière, associatedWithTaxonRank, species]
-
A.
associatedWithRank
chosen
Indicates a relationship where an entity is linked to a specific rank, level, or hierarchical position.
-
B.
hasRelatedTaxon
Indicates a taxonomic relationship between two taxa that are connected in some biologically or taxonomically relevant way, without specifying the exact nature of that relationship.
-
C.
hasTaxonomicRankAbove
Indicates that one taxonomic rank is hierarchically higher (more inclusive) than another in a classification system.
-
D.
studiedTaxonRank
Indicates that an entity’s study or research activity is specifically focused on organisms at a particular taxonomic rank (e.g., species, genus, family).
-
E.
hasMemberTaxonRank
Indicates that a group or higher-level taxon includes members classified at a specified taxonomic rank.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 21, 2026, 12:58 p.m.