Triple
T33037794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pseudogyrinocheilus |
E845366
|
entity |
| Predicate | hasGillCoverAdaptation |
P91372
|
FINISHED |
| Object | adapted for fast-flowing water |
—
|
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: adapted for fast-flowing water | Statement: [Pseudogyrinocheilus, hasGillCoverAdaptation, adapted for fast-flowing water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGillCoverAdaptation Context triple: [Pseudogyrinocheilus, hasGillCoverAdaptation, adapted for fast-flowing water]
-
A.
hasGillType
Indicates the specific type or structure of gills that an organism possesses.
-
B.
hasGillOpeningType
Indicates the specific type or form of gill opening present in an organism.
-
C.
hasGills
Indicates that an entity possesses gills as an anatomical feature used for respiration.
-
D.
hasAquaticAdaptationsIn
Indicates that an entity possesses physical or behavioral adaptations suited for living or functioning in a specified aquatic environment.
-
E.
hasOperculum
chosen
Indicates that an organism possesses an operculum, a covering or lid-like structure associated with a body part or opening.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.