Triple
T11725016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camarasaurus |
E278740
|
entity |
| Predicate | toothMorphology |
P35359
|
FINISHED |
| Object | robust, spatulate teeth suited for coarse vegetation |
—
|
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: robust, spatulate teeth suited for coarse vegetation | Statement: [Camarasaurus, toothMorphology, robust, spatulate teeth suited for coarse vegetation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toothMorphology Context triple: [Camarasaurus, toothMorphology, robust, spatulate teeth suited for coarse vegetation]
-
A.
distinguishingDentalFeature
Indicates that one entity has a dental characteristic that serves to differentiate it from another entity or group.
-
B.
dentition
chosen
Indicates the type, arrangement, or condition of teeth that an entity possesses.
-
C.
typicalLocationOfTooth
Indicates the usual or characteristic anatomical location where a tooth is found or situated.
-
D.
incisorCount
Indicates the number of incisor teeth an entity has.
-
E.
hasTeeth
Indicates that one entity possesses teeth as a physical feature.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d603cc8190b2e68d0bdd793362 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.