Triple
T10100327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Kilda Football Club |
E216182
|
entity |
| Predicate | joinedLeagueYear |
P30000
|
FINISHED |
| Object | 1897 |
—
|
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: 1897 | Statement: [St Kilda Football Club, joinedLeagueYear, 1897]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedLeagueYear Context triple: [St Kilda Football Club, joinedLeagueYear, 1897]
-
A.
joinedClubYear
Indicates the specific year in which an entity became a member of a particular club.
-
B.
joinedInYear
Indicates that an entity became a member of, or started participating in, another entity (such as an organization, group, or institution) in a specified calendar year.
-
C.
joinedLeagueInSeason
chosen
Indicates that an entity became a member of a particular league starting in a specified season.
-
D.
establishedInLeague
Indicates that an entity (such as a team or club) was founded or formally created while participating in, or as part of, a particular league.
-
E.
joinedConferenceYear
Indicates the year in which an entity became a participant or member of a particular conference.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd09878f88190bcfa2c81fb10e821 |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:02 p.m.