Triple
T162104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conference USA |
E3309
|
entity |
| Predicate | mediaRights |
P6247
|
FINISHED |
| Object | television contracts |
—
|
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: television contracts | Statement: [Conference USA, mediaRights, television contracts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaRights Context triple: [Conference USA, mediaRights, television contracts]
-
A.
mediaMarket
Indicates a relationship where a media outlet or content provider serves, targets, or operates within a particular geographic or demographic market.
-
B.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
C.
usedByMedia
Indicates that something is employed or utilized by media organizations or media-related channels.
-
D.
fareMedia
Indicates that a particular type of ticket, pass, or payment instrument is used as the medium for paying a fare.
-
E.
hasLegalDepositRightFor
Indicates that an entity holds the legal right to receive, collect, or claim deposited materials (such as publications or documents) from another entity under legal deposit regulations.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2585877648190a2ec320182a69343 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256623704819089d9eeefe05858ce |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2578329d08190be82e004b8224d2b |
completed | Feb. 28, 2026, 2:48 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.