Triple
T4572624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergiyev Posad |
E123068
|
entity |
| Predicate | historicalName |
P65
|
FINISHED |
| Object |
Sergiyev
Sergiyev is the former name of the Russian town now known as Sergiyev Posad, a historic center of Orthodox Christianity northeast of Moscow.
|
E482818
|
NE FINISHED |
How this triple was built (4 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: Sergiyev | Statement: [Sergiyev Posad, historicalName, Sergiyev]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sergiyev Context triple: [Sergiyev Posad, historicalName, Sergiyev]
-
A.
Voykovskaya
Voykovskaya is a Moscow Metro station serving the Zamoskvoretskaya Line in the northern part of the city.
-
B.
Otradnoye
Otradnoye is a town in Russia located within the Leningrad (Saint Petersburg) region, known for its position along the Neva River and proximity to Saint Petersburg.
-
C.
Otradnoye
Otradnoye is a Moscow Metro station on the Serpukhovsko–Timiryazevskaya Line serving the Otradnoye District in northern Moscow.
-
D.
Yuryev
Yuryev is a historical name for the Estonian city now known as Tartu, reflecting its past under various regional powers.
-
E.
Paveletskaya
Paveletskaya is a Moscow Metro station named after the nearby Paveletsky railway terminal, serving as a key transport hub in the city’s network.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Sergiyev Triple: [Sergiyev Posad, historicalName, Sergiyev]
Generated description
Sergiyev is the former name of the Russian town now known as Sergiyev Posad, a historic center of Orthodox Christianity northeast of Moscow.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Sergiyev Target entity description: Sergiyev is the former name of the Russian town now known as Sergiyev Posad, a historic center of Orthodox Christianity northeast of Moscow.
-
A.
Voykovskaya
Voykovskaya is a Moscow Metro station serving the Zamoskvoretskaya Line in the northern part of the city.
-
B.
Otradnoye
Otradnoye is a town in Russia located within the Leningrad (Saint Petersburg) region, known for its position along the Neva River and proximity to Saint Petersburg.
-
C.
Otradnoye
Otradnoye is a Moscow Metro station on the Serpukhovsko–Timiryazevskaya Line serving the Otradnoye District in northern Moscow.
-
D.
Yuryev
Yuryev is a historical name for the Estonian city now known as Tartu, reflecting its past under various regional powers.
-
E.
Paveletskaya
Paveletskaya is a Moscow Metro station named after the nearby Paveletsky railway terminal, serving as a key transport hub in the city’s network.
- F. None of above. chosen
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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c711408190a2b096daf57e6eac |
completed | March 20, 2026, 2:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be819fa79481908b35c424bff0c939 |
completed | March 21, 2026, 11:31 a.m. |
| NEDg | Description generation | batch_69be82c740988190b1fc8af6bafba375 |
completed | March 21, 2026, 11:36 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69be83cb23488190af7098f9d7af167f |
completed | March 21, 2026, 11:40 a.m. |
Created at: March 20, 2026, 1:10 p.m.