Triple
T20678324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1938–39 NBL season |
E508221
|
entity |
| Predicate | isProfessionalLeagueSeason |
P1219
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1938–39 NBL season, isProfessionalLeagueSeason, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProfessionalLeagueSeason Context triple: [1938–39 NBL season, isProfessionalLeagueSeason, true]
-
A.
isProfessionalLeague
Indicates that a sports league operates at a professional level, typically involving paid athletes and formal organizational structures.
-
B.
originalLeagueSeason
Indicates that a given league season is the initial or inaugural season of that league in its original form.
-
C.
includesProfessionalLeagues
Indicates that an entity contains or encompasses one or more professional sports leagues within its scope or structure.
-
D.
sportSeasonOf
Indicates that one entity is a sports season that belongs to, or is part of, the overall history or schedule of the specified sport.
-
E.
competitionSeason
chosen
Indicates that an entity is associated with a particular competitive season or edition of a competition.
- 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6bea354f0819094e9ee8d3adaa221 |
completed | April 21, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.