Triple
T35769344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swainsona tenuis |
E1034114
|
entity |
| Predicate | inGenus |
P25997
|
FINISHED |
| Object | Swainsona |
—
|
NE NERFINISHED |
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: Swainsona | Statement: [Swainsona tenuis, inGenus, Swainsona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inGenus Context triple: [Swainsona tenuis, inGenus, Swainsona]
-
A.
exampleGenus
Indicates that one entity is an example or instance illustrating the genus or general category represented by the other entity.
-
B.
hostGenus
Indicates that one entity serves as the biological host genus for another entity (such as a parasite, pathogen, or symbiont).
-
C.
anamorphGenus
Indicates that one genus is the anamorphic (asexual) form corresponding to another genus, typically its teleomorphic (sexual) form, in fungal taxonomy.
-
D.
hasGenus
chosen
Indicates that one entity belongs to, or is classified under, the biological genus represented by the other entity.
-
E.
namedAfterTypeGenus
Indicates that an entity (such as a taxonomic group) is named after its type genus.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1f64f1081908cc2774840684310 |
completed | May 3, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.