Triple
T31619613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA Digital |
E806857
|
entity |
| Predicate | hasMediaProperty |
P186360
|
FINISHED |
| Object | NBA.com |
—
|
NE NERFINISHED |
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: NBA.com | Statement: [NBA Digital, hasMediaProperty, NBA.com]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMediaProperty Context triple: [NBA Digital, hasMediaProperty, NBA.com]
-
A.
hasMediaAspect
chosen
Indicates that something possesses a particular media-related characteristic, format, or attribute.
-
B.
hasMediaAppearanceIn
Indicates that an entity appears or is featured as media content within a specified media work, program, or publication.
-
C.
hasMediaEvent
Indicates that an entity is associated with, or participates in, a specific media-related event (such as a broadcast, publication, or coverage instance).
-
D.
hasCommonMedia
Indicates that two entities share at least one media item (such as an image, video, or audio file) in common.
-
E.
hasMediaPlayer
Indicates that an entity is equipped with or associated with a media player capable of playing audio or video 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: April 30, 2026, 10:40 p.m.