Triple

T26481614
Position Surface form Disambiguated ID Type / Status
Subject Beklemishevskaya Tower E664700 entity
Predicate alsoKnownAs P39 FINISHED
Object Moskvoretskaya Tower
Moskvoretskaya Tower is a historic corner tower of the Moscow Kremlin, notable for its strategic riverside location and distinctive medieval fortification architecture.
E1737139 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: Moskvoretskaya Tower | Statement: [Beklemishevskaya Tower, alsoKnownAs, Moskvoretskaya Tower]
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: Moskvoretskaya Tower
Triple: [Beklemishevskaya Tower, alsoKnownAs, Moskvoretskaya Tower]
Generated description
Moskvoretskaya Tower is a historic corner tower of the Moscow Kremlin, notable for its strategic riverside location and distinctive medieval fortification architecture.

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_69ee883bc85481909885f92415cbce33 completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f612fafa5481908a921332952b448f completed May 2, 2026, 3:06 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11fe577bb88190af3b9f55de3a88cb completed May 23, 2026, 7:21 p.m.
NEDg Description generation batch_6a11ffac92d48190a9bed111a9aadfb1 completed May 23, 2026, 7:27 p.m.
NED2 Entity disambiguation (via description) batch_6a12003230608190a8a471769f896bb2 completed May 23, 2026, 7:29 p.m.
Created at: April 27, 2026, 12:27 a.m.