Triple
T5295212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBL Most Valuable Player |
E119835
|
entity |
| Predicate | lastWinnerSeason |
P63378
|
FINISHED |
| Object | 1948–49 NBL season |
—
|
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: 1948–49 NBL season | Statement: [NBL Most Valuable Player, lastWinnerSeason, 1948–49 NBL season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastWinnerSeason Context triple: [NBL Most Valuable Player, lastWinnerSeason, 1948–49 NBL season]
-
A.
lastSeasonChampion
Indicates that the subject is the champion or winner of the immediately preceding season of the relevant competition or event.
-
B.
lastWinner
Indicates that one entity is the most recent winner in a sequence of competitions, contests, or events involving the other entity.
-
C.
seasonChampion
Indicates that an entity is the winner or champion of a particular season of a competition, league, or series.
-
D.
finalsChampion
Indicates that an entity is the winner or champion of a particular final match, series, or tournament.
-
E.
championPreviousTitleSeason
Indicates that an entity was the champion of the immediately preceding season for a given title or competition.
- F. None of above. chosen
Provenance (4 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8682d18c8190bbb35cc75c8a7c12 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd844dfdac819086efedd1cbebff84 |
completed | March 20, 2026, 5:30 p.m. |
| PDg | Predicate description generation | batch_69bd86800630819096dad2eb2248c372 |
completed | March 20, 2026, 5:40 p.m. |
Created at: March 20, 2026, 1:52 p.m.