Triple
T16186440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zelenograd |
E392816
|
entity |
| Predicate | incorporatedIntoMoscow |
P122072
|
FINISHED |
| Object | 1963 |
—
|
LITERAL 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: 1963 | Statement: [Zelenograd, incorporatedIntoMoscow, 1963]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorporatedIntoMoscow Context triple: [Zelenograd, incorporatedIntoMoscow, 1963]
-
A.
joinedRussianEmpire
Indicates that an entity became part of, or was incorporated into, the Russian Empire.
-
B.
reignAsGrandPrinceOfMoscowFrom
Indicates that a person held the position of Grand Prince of Moscow starting from a specified time.
-
C.
incorporatedIntoVienna
Indicates that one entity (typically a place or administrative unit) has been formally merged into and made part of the city of Vienna.
-
D.
citySovietName
Indicates that a city has or had an official or commonly used name during the Soviet era.
-
E.
isFirstRussianSettlementIn
Indicates that a settlement is the earliest Russian-established settlement within a specified geographic or political area.
- F. None of above. chosen
Provenance (4 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22061f47481909ededd5eed40f5a4 |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.