Triple
T15606397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bastia Umbra |
E375169
|
entity |
| Predicate | dialingCodeSystem |
P45385
|
FINISHED |
| Object | Italian 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: Italian telephone numbering plan | Statement: [Bastia Umbra, dialingCodeSystem, Italian telephone numbering plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dialingCodeSystem Context triple: [Bastia Umbra, dialingCodeSystem, Italian telephone numbering plan]
-
A.
UICCountryCode
Indicates that an entity is associated with a specific country identified by its UIC (International Union of Railways) country code.
-
B.
callingCodeType
Indicates the type or category of a telephone calling code associated with an entity.
-
C.
callingCode
Indicates the telephone country or area code associated with an entity for making phone calls.
-
D.
continentCode
Indicates the standardized code assigned to the continent with which an entity is associated.
-
E.
regionCodeSystem
chosen
Indicates that a region is identified or classified according to a particular coding system for geographic or administrative areas.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e7ec08c8190b3842cf3043aea27 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.