Triple
T3774289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discocnide |
E83269
|
entity |
| Predicate | hasTaxonomicStatus |
P10572
|
FINISHED |
| Object | accepted genus name |
—
|
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: accepted genus name | Statement: [Discocnide, hasTaxonomicStatus, accepted genus name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTaxonomicStatus Context triple: [Discocnide, hasTaxonomicStatus, accepted genus name]
-
A.
taxonomicStatus
chosen
Indicates the formal classification status of a taxon within a taxonomic system, such as whether it is accepted, synonymized, provisional, or invalid.
-
B.
hasTaxonomicRankAbove
Indicates that one taxonomic rank is hierarchically higher (more inclusive) than another in a classification system.
-
C.
hasTaxonomicRankBelow
Indicates that one taxonomic rank is hierarchically lower (more specific) than another within a classification system.
-
D.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
-
E.
hasSubtaxon
Indicates that one taxonomic group is a subordinate or included taxon within 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_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.