Triple

T17796809
Position Surface form Disambiguated ID Type / Status
Subject Koceljeva E444313 entity
Predicate usesTelephoneCode P247 FINISHED
Object +381 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: +381 | Statement: [Koceljeva, usesTelephoneCode, +381]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesTelephoneCode
Context triple: [Koceljeva, usesTelephoneCode, +381]
  • 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. areaCode
    Indicates that a location, phone number, or region is associated with a specific telephone area code.
  • D. nationalPrefixForDomesticCalls
    Indicates the dialing prefix that must be used when making domestic telephone calls within a given country or numbering plan.
  • E. continentCode
    Indicates the standardized code assigned to the continent with which an entity is associated.
  • 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_69d8b9efe370819095cd219b143ae727 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e487fbc83481909a30fc7203b64099 completed April 19, 2026, 7:44 a.m.
PD Predicate disambiguation batch_69e3d8de28688190844b65acf6af54e6 completed April 18, 2026, 7:17 p.m.
Created at: April 10, 2026, 10:13 a.m.