Triple
T15967487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discocnide mexicana |
E387230
|
entity |
| Predicate | isMonotypicGenusTypeSpecies |
P7381
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Discocnide mexicana, isMonotypicGenusTypeSpecies, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMonotypicGenusTypeSpecies Context triple: [Discocnide mexicana, isMonotypicGenusTypeSpecies, yes]
-
A.
isOnlyGenusIn
Indicates that a genus is the sole genus contained within a specified higher-level taxonomic group or context.
-
B.
hasGenus
Indicates that one entity belongs to, or is classified under, the biological genus represented by the other entity.
-
C.
isMonophyletic
Indicates that a group of organisms includes a common ancestor and all of its descendants, forming a single complete branch on the tree of life.
-
D.
typeSpecies
chosen
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a higher-level group (such as a genus).
-
E.
hasSolitarySpecies
Indicates that an entity includes or is associated with species that live or behave predominantly alone rather than in groups.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.