Triple
T3653728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epigonichthys |
E77479
|
entity |
| Predicate | hasDigestiveSystem |
P19652
|
FINISHED |
| Object | complete digestive tract |
—
|
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 digestive tract | Statement: [Epigonichthys, hasDigestiveSystem, complete digestive tract]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigestiveSystem Context triple: [Epigonichthys, hasDigestiveSystem, complete digestive tract]
-
A.
digestiveSystem
chosen
Indicates the relationship in which an entity possesses or is associated with a system responsible for breaking down food and absorbing nutrients.
-
B.
hasExcretorySystem
Indicates that an organism possesses a biological system responsible for eliminating metabolic waste products from its body.
-
C.
digestiveMethod
Indicates the way or process by which an entity digests or breaks down food or nutrients.
-
D.
hasStomachType
Indicates that an entity possesses or is characterized by a specific type or classification of stomach.
-
E.
hasRespiratorySystem
Indicates that an entity possesses a respiratory system, i.e., anatomical structures enabling breathing and gas exchange.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3b9164c81908938a4338430d193 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.