Triple
T31770259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plagopterinae |
E810918
|
entity |
| Predicate | bodyWaterPreference |
P125062
|
FINISHED |
| Object | warmwater streams |
—
|
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: warmwater streams | Statement: [Plagopterinae, bodyWaterPreference, warmwater streams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyWaterPreference Context triple: [Plagopterinae, bodyWaterPreference, warmwater streams]
-
A.
prefersWater
chosen
Indicates a relationship where an entity favors or chooses water over other available options.
-
B.
hydrationSupport
Indicates that one entity provides or enhances the hydration of another entity, helping to maintain or improve its water balance.
-
C.
bodyWaterClaimedBy
Indicates that a particular body of water is asserted or designated as being owned, controlled, or claimed by a specific entity.
-
D.
hydrationState
Indicates the current level or condition of how much water or fluid an entity contains or has available.
-
E.
waterRequirement
Indicates the amount or conditions of water needed for an entity to grow, function, or be maintained properly.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaf024c8190bdcb4ffead3118a5 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:33 p.m.