Triple
T8564165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Sakakawea |
E202762
|
entity |
| Predicate | fishSpecies |
P7733
|
FINISHED |
| Object | northern pike |
E222688
|
NE 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: northern pike | Statement: [Lake Sakakawea, fishSpecies, northern pike]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: northern pike Context triple: [Lake Sakakawea, fishSpecies, northern pike]
-
A.
northern pike
chosen
The northern pike is a large, predatory freshwater fish known for its elongated body, sharp teeth, and ambush-hunting behavior in lakes and rivers across the Northern Hemisphere.
-
B.
Walleye
The walleye is a popular North American freshwater game fish prized by anglers for its excellent taste and challenging sport.
-
C.
Pike
Pike is an English surname of Old English origin, often associated with people who lived near a pointed hill or carried a pike as a weapon.
-
D.
walleye
Walleye is the internal codename used by Google for its Pixel 2 smartphone model.
-
E.
Muskie
Muskie is a surname most notably associated with Edmund Muskie, a prominent American politician and former U.S. Secretary of State.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe9d11274819099cc33a21a993a1f |
completed | March 31, 2026, 3:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce895f91bc819099b1b2df59374403 |
completed | April 2, 2026, 3:21 p.m. |
Created at: March 30, 2026, 6:20 p.m.