Triple
T35948253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hionanthera |
E1039643
|
entity |
| Predicate | belongsToTaxonomicGroup |
P16820
|
FINISHED |
| Object | flowering plants |
—
|
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: flowering plants | Statement: [Hionanthera, belongsToTaxonomicGroup, flowering plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToTaxonomicGroup Context triple: [Hionanthera, belongsToTaxonomicGroup, flowering plants]
-
A.
taxonGroup
chosen
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
B.
hasImportantTaxonGroup
Indicates that an entity is associated with a taxonomic group considered particularly significant or relevant in a given biological or classification context.
-
C.
hasClassifiedTaxon
Indicates that an entity has assigned or associated a specific taxonomic classification to another entity.
-
D.
includesTaxaWith
Indicates that an entity contains or encompasses one or more specified taxa within its scope or membership.
-
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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
Created at: May 3, 2026, 4:07 p.m.