Triple
T24956094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embassy of Russia in Washington, D.C. |
E624474
|
entity |
| Predicate | hasTelephonePrefix |
P190
|
FINISHED |
| Object | +1 202 |
—
|
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: +1 202 | Statement: [Embassy of Russia in Washington, D.C., hasTelephonePrefix, +1 202]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTelephonePrefix Context triple: [Embassy of Russia in Washington, D.C., hasTelephonePrefix, +1 202]
-
A.
hasTelephoneService
Indicates that a subject is provided with or connected to telephone service.
-
B.
nationalPrefixForDomesticCalls
Indicates the dialing prefix that must be used when making domestic telephone calls within a given country or numbering plan.
-
C.
hasAreaCode
chosen
Indicates that a specified telephone area code is assigned to or associated with a particular geographic region, location, or phone service entity.
-
D.
hasPostalCodePrefix
Indicates that a location’s postal code begins with a specified sequence of characters.
-
E.
associatedCountryCodePrefix
Indicates that one entity has a country code prefix that is associated with, or corresponds to, the other entity.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 5:57 a.m.