Triple
T26488165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zalesye region |
E664883
|
entity |
| Predicate | laterPoliticalCenter |
P19570
|
FINISHED |
| Object | Moscow |
—
|
NE NERFINISHED |
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: Moscow | Statement: [Zalesye region, laterPoliticalCenter, Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPoliticalCenter Context triple: [Zalesye region, laterPoliticalCenter, Moscow]
-
A.
politicalCenterDuring
Indicates that an entity serves as the primary political center or seat of political authority for another entity during a specified time period.
-
B.
laterPoliticalEntity
Indicates that one political entity succeeds or replaces another in time, coming into existence or power at a later point.
-
C.
laterSeatOfGovernment
chosen
Indicates that the referenced place served as a subsequent seat of government for the same political entity after an earlier one.
-
D.
politicalCenterShiftedFrom
Indicates that the primary political center or seat of power moved from one location or entity to another.
-
E.
mainPoliticalDevelopment
Indicates the primary or most significant political change, event, or evolution affecting an entity within a given period or context.
- F. None of above.
Provenance (3 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_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 27, 2026, 12:32 a.m.