Triple
T38260871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iliad Italia |
E1017923
|
entity |
| Predicate | offersUnlimitedSMSInItaly |
P198072
|
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, offersUnlimitedSMSInItaly, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersUnlimitedSMSInItaly Context triple: [Iliad Italia, offersUnlimitedSMSInItaly, yes]
-
A.
offersUnlimitedCallsInItaly
Indicates that the subject provides a service allowing unlimited phone calls within Italy.
-
B.
supportsSMS
Indicates that one entity provides the capability for another entity to send, receive, or otherwise use SMS (Short Message Service) messaging.
-
C.
advantageOverSMS
Indicates that one communication method or system has benefits or superior qualities compared to SMS.
-
D.
hasLimitedInternationalConnections
Indicates that an entity maintains only a small, restricted, or less extensive set of relationships or interactions with foreign or international counterparts.
-
E.
smsCapacity
Indicates the maximum number of SMS messages that can be stored, sent, or handled within a given system or 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_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
| PDg | Predicate description generation | batch_69fec5c3f8248190b835a8e4eba470c4 |
completed | May 9, 2026, 5:27 a.m. |
Created at: May 3, 2026, 4:30 p.m.