Triple
T29034750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myosciurus |
E737826
|
entity |
| Predicate | hasScientificNameOfTypeSpecies |
P120647
|
FINISHED |
| Object | Myosciurus pumilio |
—
|
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: Myosciurus pumilio | Statement: [Myosciurus, hasScientificNameOfTypeSpecies, Myosciurus pumilio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScientificNameOfTypeSpecies Context triple: [Myosciurus, hasScientificNameOfTypeSpecies, Myosciurus pumilio]
-
A.
hasScientificSpecies
Indicates that an entity is associated with a specific scientific (Latin) species name.
-
B.
hasScientificDesignation
Indicates that an entity is associated with a specific formal scientific name or designation used in scientific classification or nomenclature.
-
C.
isTypeSpeciesOfGenus
chosen
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a particular genus.
-
D.
scientificName
Indicates the formal taxonomic name assigned to an organism according to scientific naming conventions.
-
E.
hasSpeciesRole
Indicates that an entity plays a specific functional or categorical role within a particular species.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 28, 2026, 9:57 a.m.