Triple

T30573530
Position Surface form Disambiguated ID Type / Status
Subject Aviamotornaya area E778180 entity
Predicate centeredAround P1939 FINISHED
Object Aviamotornaya metro station
Aviamotornaya metro station is a Moscow Metro station that serves as the main transport hub and namesake for the surrounding Aviamotornaya area.
E1941222 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: Aviamotornaya metro station | Statement: [Aviamotornaya area, centeredAround, Aviamotornaya metro 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: Aviamotornaya metro station
Triple: [Aviamotornaya area, centeredAround, Aviamotornaya metro station]
Generated description
Aviamotornaya metro station is a Moscow Metro station that serves as the main transport hub and namesake for the surrounding Aviamotornaya 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_69f2249f8c148190ae7eb3912cde112a completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6891536e08190afce308c5196b020 completed May 2, 2026, 11:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a28fb91dc1c8190918a5efde32f7ef4 completed June 10, 2026, 5:52 a.m.
NEDg Description generation batch_6a28fc6062c48190a6efa06c4fe2129b completed June 10, 2026, 5:55 a.m.
NED2 Entity disambiguation (via description) batch_6a28fe10d1288190a5061285848dbe74 completed June 10, 2026, 6:02 a.m.
Created at: April 29, 2026, 8:22 p.m.