Triple
T16934092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleginus gracilis |
E410785
|
entity |
| Predicate | foundInWaterType |
P75237
|
FINISHED |
| Object | cold water |
—
|
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: cold water | Statement: [Eleginus gracilis, foundInWaterType, cold water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInWaterType Context triple: [Eleginus gracilis, foundInWaterType, cold water]
-
A.
isAquatic
Indicates that an entity primarily lives in or is adapted to water environments.
-
B.
locatedInWaterBodyType
chosen
Indicates that an entity is situated within or on a body of water of a specified type (e.g., lake, river, ocean).
-
C.
waterContains
Indicates that a body or volume of water holds, includes, or has within it a specified substance, object, or entity.
-
D.
containsAquaticMembers
Indicates that a group or collection includes one or more members that live in or are adapted to aquatic environments.
-
E.
hasAquaticAdaptationsIn
Indicates that an entity possesses physical or behavioral adaptations suited for living or functioning in a specified aquatic 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2714b08190a2524d5d9578cc87 |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.