Triple
T33813386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israeli Basketball League Cup |
E866599
|
entity |
| Predicate | featuresTopClubs |
P50991
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Israeli Basketball League Cup, featuresTopClubs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTopClubs Context triple: [Israeli Basketball League Cup, featuresTopClubs, yes]
-
A.
topClubsParticipateIn
Indicates that leading or highest-ranked clubs take part in a specified event, competition, or activity.
-
B.
featuresClubs
chosen
Indicates that something includes or presents one or more clubs as part of its composition, content, or offering.
-
C.
otherProminentClub
Indicates a relationship where an entity is associated with another club that is also notable or high-profile, distinct from its primary or main club.
-
D.
mostSuccessfulClub
Indicates that one club holds the highest level of success (e.g., by titles, achievements, or performance) compared to all other clubs in the given context.
-
E.
featuresTopPlayers
Indicates that something prominently presents or showcases the most outstanding or highly ranked players.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0226c8b2f881909de3c1a5ba40fc49 |
completed | May 11, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_6a0225602acc8190978ab4aacc615b8d |
completed | May 11, 2026, 6:52 p.m. |
Created at: May 1, 2026, 1:46 a.m.