Triple

T38658137
Position Surface form Disambiguated ID Type / Status
Subject Vyborg Bay E939953 entity
Predicate hasPort P35 FINISHED
Object Port of Vyborg
The Port of Vyborg is a commercial seaport in the Russian town of Vyborg that serves as an important maritime hub for cargo traffic in the eastern Gulf of Finland near the Russian-Finnish border.
E2281765 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: Port of Vyborg | Statement: [Vyborg Bay, hasPort, Port of Vyborg]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Port of Vyborg
Triple: [Vyborg Bay, hasPort, Port of Vyborg]
Generated description
The Port of Vyborg is a commercial seaport in the Russian town of Vyborg that serves as an important maritime hub for cargo traffic in the eastern Gulf of Finland near the Russian-Finnish border.

Provenance (5 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_69f76ede49648190a48bfe47032a05a3 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcdbebb5c08190b3736050ea295639 completed May 7, 2026, 6:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a4205bc44908190a2f5f1d897cc1bff completed June 29, 2026, 5:42 a.m.
NEDg Description generation batch_6a42098981b081909b7e4b8d8f5a7560 completed June 29, 2026, 5:58 a.m.
NED2 Entity disambiguation (via description) batch_6a420a03a6b481908e744078fbf57edc completed June 29, 2026, 6 a.m.
Created at: May 3, 2026, 4:33 p.m.