Triple
T2314775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathartidae |
E51037
|
entity |
| Predicate | thermoregulationBehavior |
P9108
|
FINISHED |
| Object | urohydrosis |
—
|
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: urohydrosis | Statement: [Cathartidae, thermoregulationBehavior, urohydrosis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thermoregulationBehavior Context triple: [Cathartidae, thermoregulationBehavior, urohydrosis]
-
A.
bodyTemperatureRegulation
chosen
Indicates how an entity controls or maintains its internal body temperature in response to environmental conditions.
-
B.
thermoregulationOfNest
Indicates the relationship in which an entity regulates or influences the temperature conditions within a nest.
-
C.
baskingBehavior
Indicates engaging in a behavior of lying or resting in warmth or light, typically to absorb heat or comfort.
-
D.
usesThermals
Indicates that one entity relies on rising warm air currents (thermals) as a means to gain lift, move, or maintain altitude.
-
E.
thermalControl
Indicates a relationship where one entity regulates, adjusts, or maintains the temperature or thermal conditions of another entity or environment.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.