Triple
T14407002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014–15 NBA G League season |
E357224
|
entity |
| Predicate | featuresParticipantsType |
P6384
|
FINISHED |
| Object | NBA prospects |
—
|
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 prospects | Statement: [2014–15 NBA G League season, featuresParticipantsType, NBA prospects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresParticipantsType Context triple: [2014–15 NBA G League season, featuresParticipantsType, NBA prospects]
-
A.
participantType
chosen
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
B.
featuresContestants
Indicates that something (such as an event, show, or competition) includes or presents certain individuals as contestants.
-
C.
featuresContestantsFrom
Indicates that something, typically a show or event, includes contestants originating from a specified source or group.
-
D.
featuresCastType
Indicates that one entity includes or highlights a particular type or category of cast (e.g., actors or performers) associated with it.
-
E.
eventParticipant
Indicates that an entity takes part in, is involved in, or participates in a particular 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de908804048190a4fe58afc2e0a5b6 |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa1b57881909a033eac8545c417 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:17 a.m.