Triple
T32940538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maylandia zebra |
E842651
|
entity |
| Predicate | aquariumTemperatureRange |
P95121
|
FINISHED |
| Object | approximately 24–28 °C |
—
|
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: approximately 24–28 °C | Statement: [Maylandia zebra, aquariumTemperatureRange, approximately 24–28 °C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aquariumTemperatureRange Context triple: [Maylandia zebra, aquariumTemperatureRange, approximately 24–28 °C]
-
A.
livesInWaterTemperature
Indicates that an entity inhabits or exists in water characterized by a specific temperature or temperature range.
-
B.
aquariumRequirement
chosen
Indicates that an entity has specific needs or conditions related to being kept in an aquarium.
-
C.
humidityRange
Indicates the range of humidity values within which a condition, process, or entity is defined, operates, or remains valid.
-
D.
aquariumCareLevel
Indicates the level of difficulty or amount of effort required to properly care for and maintain an aquarium.
-
E.
growthTemperatureRange
Indicates the range of temperatures within which an organism or entity can grow or function effectively.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:20 a.m.