Triple

T26505400
Position Surface form Disambiguated ID Type / Status
Subject Federal highway A147 E669529 entity
Predicate regionServed P82 FINISHED
Object Tuapse district
Tuapse district is a coastal administrative region in Russia’s Krasnodar Krai on the Black Sea, known for its port town of Tuapse and role as a transport and resort area.
E1861709 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: Tuapse district | Statement: [Federal highway A147, regionServed, Tuapse district]
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: Tuapse district
Triple: [Federal highway A147, regionServed, Tuapse district]
Generated description
Tuapse district is a coastal administrative region in Russia’s Krasnodar Krai on the Black Sea, known for its port town of Tuapse and role as a transport and resort area.

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_6a25a82c50508190adc6b7453185b9c4 completed June 7, 2026, 5:19 p.m.
NEDg Description generation batch_6a25ac6034a081909518662153fbe1b3 completed June 7, 2026, 5:37 p.m.
NED2 Entity disambiguation (via description) batch_6a25b146e9d0819086b956ae8ea30aab completed June 7, 2026, 5:58 p.m.
Created at: April 27, 2026, 1:16 a.m.