Triple
T38155680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colignonia parviflora |
E952878
|
entity |
| Predicate | hasParentTaxon |
P2891
|
FINISHED |
| Object | Colignonia |
—
|
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: Colignonia | Statement: [Colignonia parviflora, hasParentTaxon, Colignonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentTaxon Context triple: [Colignonia parviflora, hasParentTaxon, Colignonia]
-
A.
parentTaxon
chosen
Indicates that one taxonomic group is the immediate higher-level (parent) taxon of another taxonomic group.
-
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.
hasSubtaxon
Indicates that one taxonomic group is a subordinate or included taxon within another taxonomic group.
-
D.
hasTaxonomicRankAbove
Indicates that one taxonomic rank is hierarchically higher (more inclusive) than another in a classification system.
-
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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0076c0a5c4819088b17b95511b93ed |
completed | May 10, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_6a007638a67c81909c091335142260ab |
completed | May 10, 2026, 12:12 p.m. |
Created at: May 3, 2026, 4:21 p.m.