Triple
T28831646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treeshrew |
E728064
|
entity |
| Predicate | scientificNameOfOrder |
P16820
|
FINISHED |
| Object | Scandentia |
—
|
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: Scandentia | Statement: [Treeshrew, scientificNameOfOrder, Scandentia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scientificNameOfOrder Context triple: [Treeshrew, scientificNameOfOrder, Scandentia]
-
A.
typeSpeciesOfOrder
Indicates that a species is the designated type species that defines and represents a particular biological order.
-
B.
insectOrderCommonName
Indicates the common (non-scientific) name of the insect order to which an insect belongs.
-
C.
isMostSpeciesRichOrderOf
Indicates that one taxonomic order has the highest number of species within the compared group or higher taxonomic rank.
-
D.
taxonGroup
chosen
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
E.
suborder
Indicates that one entity is a more specific, subordinate ordering or arrangement within the broader ordering defined by another entity.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 6:38 a.m.