Triple
T16392699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gastrotricha |
E398092
|
entity |
| Predicate | digestiveTract |
P58139
|
FINISHED |
| Object | complete with mouth and anus |
—
|
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: complete with mouth and anus | Statement: [Gastrotricha, digestiveTract, complete with mouth and anus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digestiveTract Context triple: [Gastrotricha, digestiveTract, complete with mouth and anus]
-
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.
digestiveMethod
Indicates the way or process by which an entity digests or breaks down food or nutrients.
-
C.
stomachType
Indicates the kind or classification of stomach an entity has, typically describing its structural or functional type.
-
D.
gutType
chosen
Indicates the type or classification of a digestive tract or gut associated with an entity.
-
E.
isExcretedVia
Indicates that a substance or waste product leaves an organism’s body through a specified anatomical route or excretory mechanism.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e326447a7481909feac905edc707ec |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.