Triple
T30424850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embassy of Cuba in Moscow |
E773996
|
entity |
| Predicate | capitalOfAccreditedCountry |
P187048
|
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: [Embassy of Cuba in Moscow, capitalOfAccreditedCountry, Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfAccreditedCountry Context triple: [Embassy of Cuba in Moscow, capitalOfAccreditedCountry, Moscow]
-
A.
capitalOfGoverningCountry
Indicates that a city serves as the capital of the country that governs a given territory or region.
-
B.
capitalCountry
Indicates that one place serves as the capital city of a given country.
-
C.
governingCountryCapitalLocatedIn
Indicates that the capital city of a governing country is geographically located within a specified territory or region.
-
D.
administeringCountryCapital
Indicates that one entity is the capital city of the country that administers or governs another entity (such as a territory or dependency).
-
E.
awardingCountryCapital
Indicates the relationship where a capital city serves as the administrative center of the country that grants or confers an award.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: April 29, 2026, 8:06 p.m.