Triple
T9099444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dremomys |
E218113
|
entity |
| Predicate | containsTaxon |
P9413
|
FINISHED |
| Object | Dremomys gularis |
E218113
|
NE 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: Dremomys gularis | Statement: [Dremomys, containsTaxon, Dremomys gularis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dremomys gularis Context triple: [Dremomys, containsTaxon, Dremomys gularis]
-
A.
Dremomys
chosen
Dremomys is a genus of forest-dwelling rodents commonly known as Asian red-cheeked squirrels, found primarily in South and Southeast Asia.
-
B.
Petinomys
Petinomys is a genus of small flying squirrels known for their gliding membranes and nocturnal, arboreal lifestyle in Asian forests.
-
C.
Aeromys
Aeromys is a genus of large flying squirrels native to Southeast Asia, known for their gliding membranes and nocturnal, arboreal lifestyle.
-
D.
Syntheosciurus
Syntheosciurus is a small genus of tree squirrels in the tribe Sciurini, known from Central American montane forests.
-
E.
Otosciurus
Otosciurus is a genus of tree squirrels within the tribe Sciurini, comprising species of small to medium-sized rodents typically found in forested habitats.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc9710ac04819096b9c8d3399b9c35 |
completed | April 1, 2026, 3:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d054455e10819095738caf0d5795e2 |
completed | April 3, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:15 p.m.