Triple
T3243557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liman Current |
E68018
|
entity |
| Predicate | namedAfterRegion |
P63
|
FINISHED |
| Object | Liman Bay region of the Russian Far East |
—
|
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: Liman Bay region of the Russian Far East | Statement: [Liman Current, namedAfterRegion, Liman Bay region of the Russian Far East]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterRegion Context triple: [Liman Current, namedAfterRegion, Liman Bay region of the Russian Far East]
-
A.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
-
B.
namedAfter
chosen
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
C.
regionName
Indicates the name assigned to a specific geographic or administrative region.
-
D.
nameDayRegion
Indicates the region or geographic area in which a particular name day is observed or recognized.
-
E.
hasRegionalName
Indicates that an entity is known by a specific name or designation within a particular region or locality.
- 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf1856708190b072efbb27920ade |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41837e48190933572165be0ca38 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:08 p.m.