Triple
T19085667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharks |
E467141
|
entity |
| Predicate | haveMetabolism |
P29817
|
FINISHED |
| Object | mostly ectothermic |
—
|
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: mostly ectothermic | Statement: [Sharks, haveMetabolism, mostly ectothermic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveMetabolism Context triple: [Sharks, haveMetabolism, mostly ectothermic]
-
A.
metabolismType
chosen
Indicates the kind of metabolic process or pathway an entity uses to obtain and transform energy or nutrients.
-
B.
isMetabolizedBy
Indicates that a substance is biochemically broken down or transformed through metabolic processes carried out by a specified organism, cell type, or enzyme system.
-
C.
hasActiveMetabolite
Indicates that a substance produces one or more metabolites that remain pharmacologically active in the body.
-
D.
energyExchangeAbility
Indicates the capacity of one entity to transfer, share, or convert energy with another entity within a given context.
-
E.
metabolicDiversity
Indicates the range and variety of metabolic pathways or processes that an entity can perform or participate in.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e346f57c8190a6299e09a0be9e05 |
completed | April 20, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.