Triple
T28091509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Cup (basketball) |
E709964
|
entity |
| Predicate | participantsFromLeague |
P51847
|
FINISHED |
| Object | Lega Basket Serie A |
—
|
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: Lega Basket Serie A | Statement: [Italian Cup (basketball), participantsFromLeague, Lega Basket Serie A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantsFromLeague Context triple: [Italian Cup (basketball), participantsFromLeague, Lega Basket Serie A]
-
A.
tier3LeagueParticipants
Indicates that the related entities are participants in a third-tier league within a competitive or organizational hierarchy.
-
B.
teamsParticipated
Indicates that the referenced teams took part in a particular event, activity, or competition.
-
C.
associatedLeagueTeam
Indicates that one entity is a sports team that is formally linked or affiliated with a particular league.
-
D.
teamParticipated
Indicates that a team took part in or was involved in a particular event, activity, or competition.
-
E.
memberOfSportsLeague
chosen
Indicates that an entity is formally part of, or participates as a member in, a specific sports league.
- 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_69ef9b70fd108190a875953b2e50ca91 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 27, 2026, 8:58 p.m.