Triple
T14376703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiscali UK |
E356492
|
entity |
| Predicate | offeredContractType |
P405
|
FINISHED |
| Object | monthly subscription |
—
|
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: monthly subscription | Statement: [Tiscali UK, offeredContractType, monthly subscription]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredContractType Context triple: [Tiscali UK, offeredContractType, monthly subscription]
-
A.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
-
B.
offersEnrollmentType
Indicates that an entity provides or makes available a specific type or category of enrollment option.
-
C.
typeOfContract
chosen
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
D.
offersPlanType
Indicates that one entity provides or makes available a specific type of plan to another entity or in a given context.
-
E.
offeredEngineType
Indicates that a particular type of engine is made available or provided as an option in a given context.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900949fc81909be0da1734c46645 |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.