Triple
T590089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meconopsis |
E17246
|
entity |
| Predicate | taxonomicNote |
P12461
|
FINISHED |
| Object | has undergone several taxonomic revisions |
—
|
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: has undergone several taxonomic revisions | Statement: [Meconopsis, taxonomicNote, has undergone several taxonomic revisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxonomicNote Context triple: [Meconopsis, taxonomicNote, has undergone several taxonomic revisions]
-
A.
taxonomicStatus
Indicates the formal classification status of a taxon within a taxonomic system, such as whether it is accepted, synonymized, provisional, or invalid.
-
B.
systematicsNote
chosen
Indicates that there is an associated comment or annotation concerning the classification or systematic arrangement of the entities involved.
-
C.
affectsTaxon
Indicates that one entity has an impact or influence on a particular taxon or group of organisms.
-
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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bb8ff0081909cd53d88930e2693 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cc13988190892ca10bd7ae9f09 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.