Triple
T23011786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAX TV |
E572923
|
entity |
| Predicate | advertisingModel |
P48652
|
FINISHED |
| Object | commercial-supported |
—
|
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: commercial-supported | Statement: [PAX TV, advertisingModel, commercial-supported]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advertisingModel Context triple: [PAX TV, advertisingModel, commercial-supported]
-
A.
usesAdvertisingModel
chosen
Indicates that one entity employs or relies on another entity’s advertising-based business or revenue model.
-
B.
adType
Indicates the classification or category of an advertisement associated with an entity or event.
-
C.
marketingModel
Indicates a relationship where an entity uses or is associated with a specific marketing model, framework, or strategy to guide promotional or market-related decisions.
-
D.
advertisingPractice
Indicates a relationship where an entity engages in or is associated with the activity, methods, or strategies of advertising.
-
E.
advertisingHistory
Indicates a relationship where one entity records or reflects the past advertising activities, campaigns, or promotional interactions associated with 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e202a481908d7a2f00a12229a0 |
completed | April 29, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.