Triple
T19676027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinohyus |
E472453
|
entity |
| Predicate | toothFunction |
P128829
|
FINISHED |
| Object | omnivorous feeding |
—
|
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: omnivorous feeding | Statement: [Dinohyus, toothFunction, omnivorous feeding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toothFunction Context triple: [Dinohyus, toothFunction, omnivorous feeding]
-
A.
toothAdaptation
chosen
Indicates how an organism’s teeth are structurally or functionally modified in response to its diet, environment, or evolutionary pressures.
-
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.
hasTeeth
Indicates that one entity possesses teeth as a physical feature.
-
D.
jawFunction
Indicates the functional role, movement, or mechanical action performed by a jaw in relation to other anatomical structures or processes.
-
E.
toothUsedToDestroy
Indicates that a tooth is employed as the means or tool to break, damage, or destroy something.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641bbea8c8190b0ad841d95068e0e |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e514eb37b8819091502cc954f70eba |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.