Triple
T38260869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iliad Italia |
E1017923
|
entity |
| Predicate | offersRoamingInEU |
P198029
|
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, offersRoamingInEU, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersRoamingInEU Context triple: [Iliad Italia, offersRoamingInEU, yes]
-
A.
supportsRoamingWith
Indicates that one entity enables or is compatible with another entity’s ability to operate or be accessed while roaming across different networks or locations.
-
B.
supportsRoamingScenarios
Indicates that the subject is capable of functioning correctly across roaming scenarios, maintaining its behavior or services as users or devices move between locations or networks.
-
C.
refersToCountryOfOperator
Indicates that something is associated with, or points to, the country where its operating organization or operator is based.
-
D.
supportsEsim
Indicates that one entity provides compatibility with, or the ability to use, an embedded SIM (eSIM) for another entity.
-
E.
internationalUsage
Indicates that something is used or applied across multiple countries or in an international context.
- 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
| PDg | Predicate description generation | batch_69fec25e3d708190be27135c57b189a5 |
completed | May 9, 2026, 5:13 a.m. |
Created at: May 3, 2026, 4:30 p.m.