Triple
T16603924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Townsville Crocodiles |
E403401
|
entity |
| Predicate | participationStartSeason |
P43853
|
FINISHED |
| Object | 1993 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: 1993 NBL season | Statement: [Townsville Crocodiles, participationStartSeason, 1993 NBL season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participationStartSeason Context triple: [Townsville Crocodiles, participationStartSeason, 1993 NBL season]
-
A.
hasSeasonalParticipationIn
Indicates that an entity takes part in or is involved with another entity only during specific seasons or recurring seasonal periods.
-
B.
originalSeasonStart
Indicates the date or point in time when a season (such as a sports league or TV series) first began or was originally launched.
-
C.
seasonStartDate
Indicates the calendar date on which a particular season begins.
-
D.
beganInLeagueSeason
chosen
Indicates that an entity (such as a team, player, or competition) began its participation or activity during a specified league season.
-
E.
startSeason
Indicates the point in time or event at which a particular season begins.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d77d97c8190a63330897e49a9c9 |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.