Triple
T13572609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Callipepla douglasii |
E324200
|
entity |
| Predicate | hasWarmBlood |
P58588
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Callipepla douglasii, hasWarmBlood, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWarmBlood Context triple: [Callipepla douglasii, hasWarmBlood, true]
-
A.
warmBlooded
chosen
Indicates that an organism maintains a relatively constant internal body temperature through internal metabolic processes, regardless of external environmental temperatures.
-
B.
isColdBlooded
Indicates that the subject has a cold-blooded (ectothermic) physiology, relying on external sources to regulate body temperature.
-
C.
bodyTemperatureRegulation
Indicates how an entity controls or maintains its internal body temperature in response to environmental conditions.
-
D.
hasCirculatorySystem
Indicates that an entity possesses a circulatory system, i.e., an internal network for transporting blood or equivalent fluids throughout its body.
-
E.
hasTemperatureRegime
Indicates that an entity is characterized by or associated with a particular pattern or regime of temperature conditions.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0106cb48190b20eb9bda131a68a |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.