Triple
T10239602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA MIP |
E243551
|
entity |
| Predicate | appliesToCompetitionLevel |
P47878
|
FINISHED |
| Object | professional |
—
|
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: professional | Statement: [NBA MIP, appliesToCompetitionLevel, professional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToCompetitionLevel Context triple: [NBA MIP, appliesToCompetitionLevel, professional]
-
A.
appliesToCompetition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a competition.
-
B.
appliesToCompetitionFormat
Indicates that something is relevant or specifically designed for a particular competition format.
-
C.
eligibleCompetition
Indicates that an entity meets the required conditions to participate in a particular competition.
-
D.
associatedWithCompetitionLevel
chosen
Indicates that something has a relationship to, or is characterized by, a particular level or tier of competition.
-
E.
includesCompetition
Indicates that one entity contains, features, or encompasses a competition as part of its scope or 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:24 a.m.