Triple
T30922536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas |
E787766
|
entity |
| Predicate | taxonCommonNameDescribed |
P168444
|
FINISHED |
| Object | flying squirrel genus Eupetaurus |
—
|
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: flying squirrel genus Eupetaurus | Statement: [Thomas, taxonCommonNameDescribed, flying squirrel genus Eupetaurus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxonCommonNameDescribed Context triple: [Thomas, taxonCommonNameDescribed, flying squirrel genus Eupetaurus]
-
A.
describedTaxonCommonName
Indicates that a taxon is being described or referenced using its common (vernacular) name rather than its scientific name.
-
B.
taxonCommonName
chosen
Indicates that a taxonomic entity is associated with a common (vernacular) name used in everyday language.
-
C.
describedTaxon
Indicates that an entity (such as a publication or description) formally describes or establishes the referenced taxon.
-
D.
namedTaxon
Indicates that an entity is identified as, or associated with, a particular taxonomic name.
-
E.
commonNameOfGenus
Indicates that the object is a commonly used name referring to the genus specified by the subject.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692b64540819090b6fad5663d3871 |
completed | May 3, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:51 p.m.