Triple
T18173035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airtime |
E435078
|
entity |
| Predicate | contentTypeSupported |
P24486
|
FINISHED |
| Object | online videos |
—
|
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: online videos | Statement: [Airtime, contentTypeSupported, online videos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentTypeSupported Context triple: [Airtime, contentTypeSupported, online videos]
-
A.
mediaTypeRecognized
Indicates that a system has successfully identified and accepted the type or format of a given media item as valid or supported.
-
B.
mediaTypeAvailable
Indicates that a particular type or format of media is available for use, access, or distribution in the given context.
-
C.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
governsContentType
Indicates that one entity defines or controls the rules, behavior, or handling associated with a particular content type.
-
E.
hasContentType
Indicates that an entity is associated with or classified by a specific type of content.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df56d0a88190af3f407d2a3bb74f |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.