Triple
T8368132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urzhum |
E197384
|
entity |
| Predicate | telecommunicationCode |
P247
|
FINISHED |
| Object | Russian telephone code system |
—
|
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: Russian telephone code system | Statement: [Urzhum, telecommunicationCode, Russian telephone code system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telecommunicationCode Context triple: [Urzhum, telecommunicationCode, Russian telephone code system]
-
A.
callingCode
chosen
Indicates the telephone country or area code associated with an entity for making phone calls.
-
B.
callingCodeType
Indicates the type or category of a telephone calling code associated with an entity.
-
C.
telephoneStandard
Indicates that there is a relationship involving the use of a particular telephone standard or protocol for communication between entities.
-
D.
areaCode
Indicates that a location, phone number, or region is associated with a specific telephone area code.
-
E.
UICCountryCode
Indicates that an entity is associated with a specific country identified by its UIC (International Union of Railways) country code.
- 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb808e56fc81908b5d37482f29452d |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:01 p.m.