Triple
T3774311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanocnide |
E83270
|
entity |
| Predicate | nomenclaturalGroup |
P45065
|
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: [Nanocnide, nomenclaturalGroup, botanical nomenclature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nomenclaturalGroup Context triple: [Nanocnide, nomenclaturalGroup, botanical nomenclature]
-
A.
taxonGroup
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
B.
nomenclaturalCode
chosen
Indicates the formal set of naming rules or code under which an entity’s scientific or taxonomic name is established or governed.
-
C.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
-
D.
binomialName
Indicates the formal scientific name assigned to a species, typically composed of its genus and specific epithet.
-
E.
taxonomicStatus
Indicates the formal classification status of a taxon within a taxonomic system, such as whether it is accepted, synonymized, provisional, or invalid.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc594c50819099ab5ac1b82f61a6 |
completed | March 8, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.