Triple

T31055872
Position Surface form Disambiguated ID Type / Status
Subject Maskoŭskaja line E791394 entity
Predicate hasStation P35 FINISHED
Object Pralietarskaja station
Pralietarskaja station is a metro station on the Maskoŭskaja line of the Minsk Metro in Belarus.
E1952630 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: Pralietarskaja station | Statement: [Maskoŭskaja line, hasStation, Pralietarskaja station]
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: Pralietarskaja station
Triple: [Maskoŭskaja line, hasStation, Pralietarskaja station]
Generated description
Pralietarskaja station is a metro station on the Maskoŭskaja line of the Minsk Metro in Belarus.

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_69f224cb08908190ba71ad9aa87518ed completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f695441b3c8190943f67a89e070329 completed May 3, 2026, 12:22 a.m.
NED1 Entity disambiguation (via context triple) batch_6a296bc60ee4819094355ddadaae095d completed June 10, 2026, 1:51 p.m.
NEDg Description generation batch_6a296c3a92688190a7e0705e122c99fc completed June 10, 2026, 1:52 p.m.
NED2 Entity disambiguation (via description) batch_6a296cd34b648190bb1406dfce82262d completed June 10, 2026, 1:55 p.m.
Created at: April 29, 2026, 9 p.m.