Triple
T11951290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10 Play |
E284429
|
entity |
| Predicate | offersCatchUpFor |
P68242
|
FINISHED |
| Object | Network 10 broadcast shows |
—
|
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: Network 10 broadcast shows | Statement: [10 Play, offersCatchUpFor, Network 10 broadcast shows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersCatchUpFor Context triple: [10 Play, offersCatchUpFor, Network 10 broadcast shows]
-
A.
offersEdition
Indicates that one entity provides or makes available a particular version or edition of another entity.
-
B.
offersAccess
chosen
Indicates that one entity provides another entity with the ability or permission to use, enter, or interact with a resource, service, or location.
-
C.
offersServiceTo
Indicates that one entity provides or makes a service available for the benefit or use of another entity.
-
D.
offersConnectionTo
Indicates that one entity provides or enables access, linkage, or connectivity to another entity.
-
E.
offersPass
Indicates that one entity provides or makes available a pass (such as a ticket, permit, or access credential) to another entity.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90364c2608190a3946c9595c71164 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.