Triple
T8649859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eutamias |
E205070
|
entity |
| Predicate | endothermy |
P10929
|
FINISHED |
| Object | endothermic |
—
|
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: endothermic | Statement: [Eutamias, endothermy, endothermic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endothermy Context triple: [Eutamias, endothermy, endothermic]
-
A.
endothermicLineages
Indicates that the related lineages possess or are associated with endothermy (the ability to regulate and maintain a constant internal body temperature through metabolic heat).
-
B.
warmBlooded
Indicates that an organism maintains a relatively constant internal body temperature through internal metabolic processes, regardless of external environmental temperatures.
-
C.
bodyTemperatureRegulation
Indicates how an entity controls or maintains its internal body temperature in response to environmental conditions.
-
D.
isEndothermic
chosen
Indicates that an organism or system generates and maintains its body temperature internally through metabolic heat production.
-
E.
metabolismType
Indicates the kind of metabolic process or pathway an entity uses to obtain and transform energy or nutrients.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4813d0548190b203e594acc38c8f |
completed | March 31, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.