Triple

T29977493
Position Surface form Disambiguated ID Type / Status
Subject Volnovakha E761490 entity
Predicate locatedOn P40 FINISHED
Object railway line Donetsk–Mariupol
The railway line Donetsk–Mariupol is a key rail route in eastern Ukraine connecting the industrial city of Donetsk with the port city of Mariupol on the Sea of Azov.
E1895444 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: railway line Donetsk–Mariupol | Statement: [Volnovakha, locatedOn, railway line Donetsk–Mariupol]
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: railway line Donetsk–Mariupol
Triple: [Volnovakha, locatedOn, railway line Donetsk–Mariupol]
Generated description
The railway line Donetsk–Mariupol is a key rail route in eastern Ukraine connecting the industrial city of Donetsk with the port city of Mariupol on the Sea of Azov.

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_69f22467626081908d5afea489590e96 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f678d69dc88190b0c31a769272f6d6 completed May 2, 2026, 10:21 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2721fbc494819093367e27055f46cc completed June 8, 2026, 8:11 p.m.
NEDg Description generation batch_6a2724257ad88190aa9148edaeb01096 completed June 8, 2026, 8:20 p.m.
NED2 Entity disambiguation (via description) batch_6a272738fe988190ba8b43c819546bb4 completed June 8, 2026, 8:34 p.m.
Created at: April 29, 2026, 6:34 p.m.