Triple
T16089161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pusa sibirica |
E390314
|
entity |
| Predicate | commonName |
P570
|
FINISHED |
| Object | Baikal seal |
E273865
|
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: Baikal seal | Statement: [Pusa sibirica, commonName, Baikal seal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Baikal seal Context triple: [Pusa sibirica, commonName, Baikal seal]
-
A.
Baikal seal
chosen
The Baikal seal is a small, uniquely freshwater species of earless seal endemic to Russia’s Lake Baikal and adapted to its cold, deep waters.
-
B.
Caspian seal
The Caspian seal is a small, endangered earless seal species found exclusively in the landlocked Caspian Sea region.
-
C.
Ladoga ringed seal
The Ladoga ringed seal is a rare, freshwater subspecies of ringed seal found only in Russia’s Lake Ladoga and noted for its isolation and conservation concern.
-
D.
Saimaa ringed seal
The Saimaa ringed seal is a critically endangered freshwater subspecies of ringed seal found only in Finland’s Lake Saimaa.
-
E.
Shima Kustanovich
Shima Kustanovich was the wife of prominent Orthodox rabbi and halachic authority Rabbi Moshe Feinstein.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1845161908190adca2af94710b2cc |
completed | April 17, 2026, 12:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffeb934b448190a486401ac6c01065 |
completed | May 10, 2026, 2:21 a.m. |
Created at: April 10, 2026, 4:59 a.m.