Triple

T27391402
Position Surface form Disambiguated ID Type / Status
Subject Golovin Avenue E691541 entity
Predicate namedAfter P63 FINISHED
Object Count Mikhail Golovin
Count Mikhail Golovin was a Russian nobleman and statesman whose prominence and influence in public life led to places such as Golovin Avenue being named in his honor.
E1918028 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: Count Mikhail Golovin | Statement: [Golovin Avenue, namedAfter, Count Mikhail Golovin]
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: Count Mikhail Golovin
Triple: [Golovin Avenue, namedAfter, Count Mikhail Golovin]
Generated description
Count Mikhail Golovin was a Russian nobleman and statesman whose prominence and influence in public life led to places such as Golovin Avenue being named in his honor.

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_69ef520386788190bc92cfcd97ebb67a completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f62cad49348190852c7d058a5bbda3 completed May 2, 2026, 4:56 p.m.
NED1 Entity disambiguation (via context triple) batch_6a27abf4a9bc8190b5236993d9f55ff5 completed June 9, 2026, 6 a.m.
NEDg Description generation batch_6a27ae1a3784819097722737c0b949cb completed June 9, 2026, 6:09 a.m.
NED2 Entity disambiguation (via description) batch_6a27aef0046081908c95ec0fa0e0497d completed June 9, 2026, 6:13 a.m.
Created at: April 27, 2026, 12:26 p.m.