Triple
T22514889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian telephone numbering plan |
E556614
|
entity |
| Predicate | geographicNumbersStartWith |
P110655
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Italian telephone numbering plan, geographicNumbersStartWith, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicNumbersStartWith Context triple: [Italian telephone numbering plan, geographicNumbersStartWith, 0]
-
A.
icaoRegionPrefix
Indicates the regional ICAO prefix that designates the geographic or administrative region associated with an aviation-related entity.
-
B.
regionNumber
Indicates that an entity is assigned to or associated with a specific numbered region within a larger spatial or organizational division.
-
C.
provinceNumber
Indicates a relationship where an entity is assigned a specific numerical identifier corresponding to a province.
-
D.
nationalPrefixForDomesticCalls
chosen
Indicates the dialing prefix that must be used when making domestic telephone calls within a given country or numbering plan.
-
E.
hasISO3166-2CodePrefix
Indicates that one entity’s ISO 3166-2 code begins with, or is prefixed by, the code of another entity.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e2c3098819098a553133cc9515b |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.