Triple
T4014760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helinus |
E90728
|
entity |
| Predicate | isAcceptedNameIn |
P13305
|
FINISHED |
| Object | botanical nomenclature |
—
|
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: botanical nomenclature | Statement: [Helinus, isAcceptedNameIn, botanical nomenclature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAcceptedNameIn Context triple: [Helinus, isAcceptedNameIn, botanical nomenclature]
-
A.
isNickname
Indicates that one name is an informal or alternative name commonly used to refer to the same person or entity as another name.
-
B.
isRelatedName
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
-
C.
isTradeNameOf
Indicates that one name is a commercial or brand designation used for a product, substance, or entity that may also have a different generic or formal name.
-
D.
isUniqueWithinStandard
Indicates that an entity is the only one of its kind within the scope or constraints of a given standard or specification.
-
E.
nameUsedIn
chosen
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
- 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_69aed95e44088190aff7d90a151b1b20 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.