Triple
T35319310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sayanogorsk |
E1019991
|
entity |
| Predicate | telephonyCodeSystem |
P143537
|
FINISHED |
| Object | Russian telephone numbering plan |
—
|
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 numbering plan | Statement: [Sayanogorsk, telephonyCodeSystem, Russian telephone numbering plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telephonyCodeSystem Context triple: [Sayanogorsk, telephonyCodeSystem, Russian telephone numbering plan]
-
A.
telephoneDialingCodeSystem
chosen
Indicates the telephone numbering or dialing code scheme used to place calls within or to a particular region, network, or service.
-
B.
telephoneSystemCountry
Indicates that a telephone system operates within, or is associated with, a specific country.
-
C.
callingCodeType
Indicates the type or category of a telephone calling code associated with an entity.
-
D.
telephoneStandard
Indicates that there is a relationship involving the use of a particular telephone standard or protocol for communication between entities.
-
E.
callingCode
Indicates the telephone country or area code associated with an entity for making phone calls.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79096a88081908cb64c02c31c72a0 |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.