Triple
T24904477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FOM |
E623665
|
entity |
| Predicate | mediaProduct |
P18814
|
FINISHED |
| Object | Formula One TV coverage |
—
|
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: Formula One TV coverage | Statement: [FOM, mediaProduct, Formula One TV coverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaProduct Context triple: [FOM, mediaProduct, Formula One TV coverage]
-
A.
mediaWork
chosen
Indicates a relationship where one entity is a media-related work (such as a film, book, recording, or other creative media production) associated with another entity.
-
B.
mediaAssets
Indicates a relationship where one entity is associated with one or more media-related resources or files (such as images, videos, or audio).
-
C.
mediaDisplayed
Indicates that a particular piece of media is shown or presented to an audience or user in a given context.
-
D.
mediaResponse
Indicates that one entity serves as a reply or reaction in a media format (such as audio, video, or image) to another entity or communication.
-
E.
mediaDependentInterface
Indicates that one interface or interaction is contingent on, or varies according to, the characteristics or type of the media involved.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:27 a.m.