Triple
T20505820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sam Newman |
E503426
|
entity |
| Predicate | mediaDomain |
P140346
|
FINISHED |
| Object | AFL 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: AFL coverage | Statement: [Sam Newman, mediaDomain, AFL coverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaDomain Context triple: [Sam Newman, mediaDomain, AFL coverage]
-
A.
mediaOrigin
Indicates the original source or provenance from which a piece of media (such as an image, video, or audio) was derived or obtained.
-
B.
mediatisedBy
Indicates that an entity’s communication or interaction is conveyed, shaped, or influenced through a particular medium or media channel rather than occurring directly.
-
C.
mediaName
Indicates the name or title assigned to a media item (such as a work, file, or publication) in the relationship.
-
D.
mediaAssets
Indicates a relationship where one entity is associated with one or more media-related resources or files (such as images, videos, or audio).
-
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. 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dc66f00819083c804535e045545 |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:35 a.m.