Triple
T321246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Actinopterygii |
E6419
|
entity |
| Predicate | bloodTemperature |
P9108
|
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: [Actinopterygii, bloodTemperature, mostly ectothermic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bloodTemperature Context triple: [Actinopterygii, bloodTemperature, mostly ectothermic]
-
A.
coreTemperature
Indicates that an entity has a specific internal or central temperature value.
-
B.
bodyTemperatureRegulation
chosen
Indicates how an entity controls or maintains its internal body temperature in response to environmental conditions.
-
C.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
D.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
E.
highestBody
Indicates that one entity is the tallest or most elevated body (e.g., physical object, celestial body, or structural component) relative to a specified set or context.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea81a1e88190b3496070eb3d85f5 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e946607081909c8b97473aaf8d1b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.