Triple

T21766228
Position Surface form Disambiguated ID Type / Status
Subject Savitaipale E537299 entity
Predicate hasAreaCode P190 FINISHED
Object Finnish telephone numbering plan — NE NERFINISHED

How this triple was built (3 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: Finnish telephone numbering plan | Statement: [Savitaipale, hasAreaCode, Finnish telephone numbering plan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Finnish telephone numbering plan
Context triple: [Savitaipale, hasAreaCode, Finnish telephone numbering plan]
  • A. Polish telephone numbering plan
    The Polish telephone numbering plan is the national system that defines how telephone numbers are structured, assigned, and dialed throughout Poland.
  • B. Russian telephone numbering plan
    The Russian telephone numbering plan is the national system that defines how telephone numbers are structured, assigned, and dialed throughout Russia.
  • C. Dutch telephone numbering plan
    The Dutch telephone numbering plan is the national system that defines how telephone numbers in the Netherlands are structured, allocated, and dialed for both geographic and non-geographic services.
  • D. Japanese telephone numbering plan
    The Japanese telephone numbering plan is the national system that defines how telephone numbers are structured, assigned, and dialed throughout Japan, including area codes, local numbers, and special service codes.
  • E. German telephone numbering plan
    The German telephone numbering plan is the national system that defines how telephone numbers are structured, assigned, and dialed throughout Germany, including area codes and subscriber numbers.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Finnish telephone numbering plan
Target entity description: The Finnish telephone numbering plan is the national system that defines how telephone numbers are structured, assigned, and dialed throughout Finland, including regional area codes and mobile prefixes.
  • A. Polish telephone numbering plan
    The Polish telephone numbering plan is the national system that defines how telephone numbers are structured, assigned, and dialed throughout Poland.
  • B. Russian telephone numbering plan
    The Russian telephone numbering plan is the national system that defines how telephone numbers are structured, assigned, and dialed throughout Russia.
  • C. Dutch telephone numbering plan
    The Dutch telephone numbering plan is the national system that defines how telephone numbers in the Netherlands are structured, allocated, and dialed for both geographic and non-geographic services.
  • D. Japanese telephone numbering plan
    The Japanese telephone numbering plan is the national system that defines how telephone numbers are structured, assigned, and dialed throughout Japan, including area codes, local numbers, and special service codes.
  • E. German telephone numbering plan
    The German telephone numbering plan is the national system that defines how telephone numbers are structured, assigned, and dialed throughout Germany, including area codes and subscriber numbers.
  • F. None of above. chosen

Provenance (2 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_69e0c46f5d1c8190bf830409e98464e5 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f031aa9c888190887c5c1d1e3bab9f completed April 28, 2026, 4:03 a.m.
Created at: April 16, 2026, 6:51 p.m.