Triple
T1741627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruminantia |
E38245
|
entity |
| Predicate | digestiveProcess |
P4106
|
FINISHED |
| Object | rumination |
—
|
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: rumination | Statement: [Ruminantia, digestiveProcess, rumination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digestiveProcess Context triple: [Ruminantia, digestiveProcess, rumination]
-
A.
digestiveSystem
Indicates the relationship in which an entity possesses or is associated with a system responsible for breaking down food and absorbing nutrients.
-
B.
swallowed
Indicates that one entity caused another entity to pass from the mouth into the body, typically down the throat.
-
C.
dissolutionProcess
Indicates the process or sequence of actions by which something (such as a substance, organization, or relationship) is broken down, disbanded, or brought to an end.
-
D.
consumes
Indicates that one entity eats, drinks, or otherwise uses up another entity as a resource or nourishment.
-
E.
partOfProcess
chosen
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
- 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.