Triple
T14001366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biya River |
E336831
|
entity |
| Predicate | cityOnRiver |
P165
|
FINISHED |
| Object | Biysk |
E627325
|
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: Biysk | Statement: [Biya River, cityOnRiver, Biysk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Biysk Context triple: [Biya River, cityOnRiver, Biysk]
-
A.
Biysk
chosen
Biysk is a historic industrial city in southwestern Siberia, Russia, situated on the Biya River and serving as a key gateway to the Altai Mountains.
-
B.
Pechora
Pechora is a town in the Komi Republic of Russia known for its location near the Pechora River and its role as a regional transport and industrial center.
-
C.
Ozyornaya
Ozyornaya is a Moscow Metro station on the Kalininsko–Solntsevskaya Line serving the western part of the city.
-
D.
Nagatinskaya
Nagatinskaya is a Moscow Metro station serving the Serpukhovsko–Timiryazevskaya Line in the Nagatinsky Zaton area of southern Moscow.
-
E.
Novorybnaya
Novorybnaya is a small rural settlement located along the Khatanga River in the remote Arctic region of northern Siberia, Russia.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed06a50819093ddc64f55050689 |
completed | April 14, 2026, 12:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6474da3081909be6b892ef8cc73e |
completed | May 8, 2026, 4:20 a.m. |
Created at: April 9, 2026, 10:19 p.m.