Triple
T28009896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vereya |
E707386
|
entity |
| Predicate | federalSubjectCapitalDistanceFrom |
P10889
|
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: [Vereya, federalSubjectCapitalDistanceFrom, Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: federalSubjectCapitalDistanceFrom Context triple: [Vereya, federalSubjectCapitalDistanceFrom, Moscow]
-
A.
governsCapital
Indicates that a political authority or administrative body exercises governing control over a capital city.
-
B.
distanceFromCapital
chosen
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
C.
governingTerritorialCapital
Indicates that a territorial entity serves as the administrative or political capital for a governing body or jurisdiction.
-
D.
territoryCapital
Indicates that one entity is the capital city or administrative center of a specified territory.
-
E.
regionCapital
Indicates that one entity is the capital city or administrative center of a specified region.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 8:03 p.m.