Triple
T8519835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castorimorpha |
E201666
|
entity |
| Predicate | hasCharacteristicDentition |
P35359
|
FINISHED |
| Object | hypsodont or ever-growing cheek teeth in many species |
—
|
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: hypsodont or ever-growing cheek teeth in many species | Statement: [Castorimorpha, hasCharacteristicDentition, hypsodont or ever-growing cheek teeth in many species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacteristicDentition Context triple: [Castorimorpha, hasCharacteristicDentition, hypsodont or ever-growing cheek teeth in many species]
-
A.
hasTeeth
Indicates that one entity possesses teeth as a physical feature.
-
B.
distinguishingDentalFeature
Indicates that one entity has a dental characteristic that serves to differentiate it from another entity or group.
-
C.
dentition
chosen
Indicates the type, arrangement, or condition of teeth that an entity possesses.
-
D.
incisorCount
Indicates the number of incisor teeth an entity has.
-
E.
hasMandibles
Indicates that an entity possesses mandibles, i.e., jaw-like mouthparts used for biting, cutting, or holding.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe628f8c48190a35201f9fde605cc |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.