Triple
T3662604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Cuban |
E77683
|
entity |
| Predicate | sportsRole |
P19813
|
FINISHED |
| Object | NBA team owner |
—
|
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: NBA team owner | Statement: [Mark Cuban, sportsRole, NBA team owner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportsRole Context triple: [Mark Cuban, sportsRole, NBA team owner]
-
A.
sportingRoleRecognised
Indicates that a particular sporting role or position has been formally acknowledged or accepted as valid within a given context or system.
-
B.
sportsBusinessRole
chosen
Indicates a professional role or position that an entity holds within the context of sports business or the sports industry.
-
C.
sportsCareer
Indicates a relationship where an entity’s professional involvement, roles, or achievements in sports are associated with a particular sport, team, period, or competitive level.
-
D.
competitionRole
Indicates that an entity holds a specific role, position, or function within a competitive event or contest.
-
E.
sportsName
Indicates the specific sport associated with or played in a given context or event.
- 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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3fcd910819082012b10b23860aa |
completed | March 8, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.