Triple
T34962695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Могилёв-Подольский |
E1008301
|
entity |
| Predicate | имеетРегиональныйТелефонныйКод |
P190
|
FINISHED |
| Object | 4337 |
—
|
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: 4337 | Statement: [Могилёв-Подольский, имеетРегиональныйТелефонныйКод, 4337]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имеетРегиональныйТелефонныйКод Context triple: [Могилёв-Подольский, имеетРегиональныйТелефонныйКод, 4337]
-
A.
hasAreaCodeCountry
Indicates that a particular telephone area code is associated with or belongs to a specific country.
-
B.
callingCode
Indicates the telephone country or area code associated with an entity for making phone calls.
-
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.
areaCode
Indicates that a location, phone number, or region is associated with a specific telephone area code.
-
E.
nationalPrefixForDomesticCalls
Indicates the dialing prefix that must be used when making domestic telephone calls within a given country or numbering plan.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4 p.m.