Triple

T38260875
Position Surface form Disambiguated ID Type / Status
Subject Iliad Italia E1017923 entity
Predicate acceptsNumberPortability P15690 FINISHED
Object yes 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: yes | Statement: [Iliad Italia, acceptsNumberPortability, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: acceptsNumberPortability
Context triple: [Iliad Italia, acceptsNumberPortability, yes]
  • A. supportsNumberPorting chosen
    Indicates that an entity enables or allows the transfer of an existing phone number from one service or provider to another.
  • B. usesOpenNumberingPlan
    Indicates that a telecommunication system or region employs an open numbering plan, where phone numbers can vary in length rather than following a fixed-length format.
  • C. usesClosedNumberingPlan
    Indicates that a telecommunication system or network follows a closed numbering plan, where phone numbers have fixed lengths and formats without requiring variable-length dialing.
  • D. hasMVNO
    Indicates that one entity operates as a Mobile Virtual Network Operator (MVNO) using the network infrastructure or services provided by another entity.
  • E. tollFreeBridgedWith
    Indicates that a toll-free communication channel is connected or linked via a bridging mechanism to another network, system, or call path.
  • 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_69f76de33e4481909099fa812709bd42 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcc3321ef081908023590ba70ba0cf completed May 7, 2026, 4:52 p.m.
PD Predicate disambiguation batch_69fcb0fdc6e08190b05e894c59481a0d completed May 7, 2026, 3:34 p.m.
Created at: May 3, 2026, 4:30 p.m.