Triple
T28495540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australosphenida |
E721097
|
entity |
| Predicate | toothMorphologyType |
P122346
|
FINISHED |
| Object | australosphenidan molar pattern |
—
|
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: australosphenidan molar pattern | Statement: [Australosphenida, toothMorphologyType, australosphenidan molar pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toothMorphologyType Context triple: [Australosphenida, toothMorphologyType, australosphenidan molar pattern]
-
A.
distinguishingDentalFeature
Indicates that one entity has a dental characteristic that serves to differentiate it from another entity or group.
-
B.
toothAdaptation
Indicates how an organism’s teeth are structurally or functionally modified in response to its diet, environment, or evolutionary pressures.
-
C.
molarType
chosen
Indicates the specific classification or category of a molar within a dental or anatomical context.
-
D.
typicalLocationOfTooth
Indicates the usual or characteristic anatomical location where a tooth is found or situated.
-
E.
dentition
Indicates the type, arrangement, or condition of teeth that an entity possesses.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f3ed46c8190bf19437b134edcf7 |
completed | May 2, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:03 a.m.