Triple
T32138957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dicynodon |
E820850
|
entity |
| Predicate | usedToothReplacement |
P134319
|
FINISHED |
| Object | limited tooth replacement (tusks only) |
—
|
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: limited tooth replacement (tusks only) | Statement: [Dicynodon, usedToothReplacement, limited tooth replacement (tusks only)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToothReplacement Context triple: [Dicynodon, usedToothReplacement, limited tooth replacement (tusks only)]
-
A.
toothReplacement
chosen
Indicates a relationship where one tooth is substituted or restored by another tooth or dental prosthetic, replacing its function or position.
-
B.
toothUsedBy
Indicates that a tooth is utilized or employed by a particular entity (such as an organism or tool) for some function or action.
-
C.
toothUsedToDestroy
Indicates that a tooth is employed as the means or tool to break, damage, or destroy something.
-
D.
toothAdaptation
Indicates how an organism’s teeth are structurally or functionally modified in response to its diet, environment, or evolutionary pressures.
-
E.
teethSownBy
Indicates that teeth were deliberately planted or scattered by a particular agent or source.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 12:30 a.m.