Triple

T26505461
Position Surface form Disambiguated ID Type / Status
Subject Adler city center E669531 entity
Predicate near P350 FINISHED
Object Adler seafront
Adler seafront is a coastal promenade and recreational area in the Adler district of Sochi, Russia, known for its beaches, sea views, and tourist infrastructure along the Black Sea.
E1728074 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: Adler seafront | Statement: [Adler city center, near, Adler seafront]
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: Adler seafront
Triple: [Adler city center, near, Adler seafront]
Generated description
Adler seafront is a coastal promenade and recreational area in the Adler district of Sochi, Russia, known for its beaches, sea views, and tourist infrastructure along the Black Sea.

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_69eeb319ec70819090834c2591cf5f1e completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f6138d906c81909258a45100e098be completed May 2, 2026, 3:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11bb373a808190bd8218fe5573ce9b completed May 23, 2026, 2:35 p.m.
NEDg Description generation batch_6a11bf3ff19c8190a1e6c425df4984ff completed May 23, 2026, 2:52 p.m.
NED2 Entity disambiguation (via description) batch_6a11bfb901508190be75b6ffb57adf1b completed May 23, 2026, 2:54 p.m.
Created at: April 27, 2026, 1:16 a.m.