Triple
T7416425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walleye |
E171141
|
entity |
| Predicate | preferredHabitat |
P76824
|
FINISHED |
| Object | deep, cool, clear waters |
—
|
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: deep, cool, clear waters | Statement: [Walleye, preferredHabitat, deep, cool, clear waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preferredHabitat Context triple: [Walleye, preferredHabitat, deep, cool, clear waters]
-
A.
preferredClimate
Indicates the type of climate that an entity favors or is most suited to.
-
B.
featuresHabitat
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
C.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
-
D.
reproductiveHabitat
Indicates the type of environment or location where an organism carries out its reproductive activities or where its offspring develop.
-
E.
nativeToClimate
Indicates that an entity naturally originates from or is originally adapted to a specified climate or climatic region.
- F. None of above. chosen
Provenance (4 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c7ae0c8190a8348d6223aeeecc |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1c3307481909a7f6bb69d4fddac |
completed | March 27, 2026, 9:08 p.m. |
Created at: March 27, 2026, 3:11 p.m.