Triple
T1933503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alectura lathami |
E41397
|
entity |
| Predicate | incubationHeatSource |
P11950
|
FINISHED |
| Object | decomposing vegetation |
—
|
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: decomposing vegetation | Statement: [Alectura lathami, incubationHeatSource, decomposing vegetation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incubationHeatSource Context triple: [Alectura lathami, incubationHeatSource, decomposing vegetation]
-
A.
thermoregulationOfNest
Indicates the relationship in which an entity regulates or influences the temperature conditions within a nest.
-
B.
temperatureControlMethod
chosen
Indicates the method or mechanism used to regulate or maintain a desired temperature.
-
C.
emitsMoreEnergyThanItReceives
Indicates that the subject releases a greater amount of energy than it takes in from its surroundings or inputs.
-
D.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
E.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb299f3c48190a5021d320ded4405 |
completed | March 7, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.