Triple

T26962108
Position Surface form Disambiguated ID Type / Status
Subject Krasnaya Polyana E679073 entity
Predicate transportConnection P1298 FINISHED
Object A148 highway
The A148 highway is a Russian road that connects the Black Sea coastal city of Sochi with the mountain resort area of Krasnaya Polyana in the Caucasus.
E2293707 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: A148 highway | Statement: [Krasnaya Polyana, transportConnection, A148 highway]
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: A148 highway
Triple: [Krasnaya Polyana, transportConnection, A148 highway]
Generated description
The A148 highway is a Russian road that connects the Black Sea coastal city of Sochi with the mountain resort area of Krasnaya Polyana in the Caucasus.

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_69eeeb4f3a448190b1e94b2d4776c16e completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f620ec8e108190966b7b8142a3e28d completed May 2, 2026, 4:06 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7af481cfcc8190a031149e340db3e4 completed Aug. 11, 2026, 10:08 a.m.
NEDg Description generation batch_6a7af4ef3ff48190835a85f1814df407 completed Aug. 11, 2026, 10:09 a.m.
NED2 Entity disambiguation (via description) batch_6a7af54a24188190a6fffd5430a4838f completed Aug. 11, 2026, 10:11 a.m.
Created at: April 27, 2026, 6:32 a.m.