Triple
T22514892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian telephone numbering plan |
E556614
|
entity |
| Predicate | sharedCostNumbersStartWith |
P148676
|
FINISHED |
| Object | 84 |
—
|
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: 84 | Statement: [Italian telephone numbering plan, sharedCostNumbersStartWith, 84]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedCostNumbersStartWith Context triple: [Italian telephone numbering plan, sharedCostNumbersStartWith, 84]
-
A.
specialRateNumberPrefixExample
Indicates that an example phone number is provided to illustrate the prefix used for a special-rate number.
-
B.
tollFreeBridgedWith
Indicates that a toll-free communication channel is connected or linked via a bridging mechanism to another network, system, or call path.
-
C.
sharesAreaCode
Indicates that two entities have telephone numbers with the same area code.
-
D.
costSharing
Indicates how the financial burden of a cost is divided or shared among multiple parties.
-
E.
hasChargeNumber
Indicates that an entity is associated with a specific charge identifier or charge reference number.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:50 p.m.