Triple
T18280974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eir Sport |
E437860
|
entity |
| Predicate | offeredBundledWith |
P22839
|
FINISHED |
| Object | Eir broadband services |
—
|
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: Eir broadband services | Statement: [Eir Sport, offeredBundledWith, Eir broadband services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredBundledWith Context triple: [Eir Sport, offeredBundledWith, Eir broadband services]
-
A.
offeredBundle
Indicates that one entity has presented a specific combination of items or services together as a bundled offer to another entity.
-
B.
associatedOffering
chosen
Indicates a relationship where one offering is linked or connected to another offering as related or contextually relevant.
-
C.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
-
D.
offersWorksBy
Indicates that one entity makes works created by another entity available, such as for sale, display, or access.
-
E.
offeredIn
Indicates that something is made available or provided within a particular context, setting, or medium.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50056ea0481908d66bf263ac80c75 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.