Triple
T16603972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brisbane Bullets |
E403402
|
entity |
| Predicate | rejoinedLeague |
P30000
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Brisbane Bullets, rejoinedLeague, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejoinedLeague Context triple: [Brisbane Bullets, rejoinedLeague, 2016]
-
A.
rejoinedLeagueName
Indicates that an entity has returned to and become a member again of a previously left league identified by its name.
-
B.
joinedLeagueInSeason
chosen
Indicates that an entity became a member of a particular league starting in a specified season.
-
C.
playedInLeagueThatBecame
Indicates that an entity participated in a sports league which later transformed into, merged into, or was rebranded as another specified league.
-
D.
movedToLeague
Indicates that an entity changed affiliation or membership from one league to another.
-
E.
mergedLeague
Indicates that two or more sports or competitive leagues have combined into a single unified 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_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.