Triple
T16338595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Derby |
E396737
|
entity |
| Predicate | foundedForLeagueExpansion |
P62114
|
FINISHED |
| Object | Fremantle Dockers entry to AFL |
—
|
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: Fremantle Dockers entry to AFL | Statement: [Western Derby, foundedForLeagueExpansion, Fremantle Dockers entry to AFL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedForLeagueExpansion Context triple: [Western Derby, foundedForLeagueExpansion, Fremantle Dockers entry to AFL]
-
A.
foundedAsExpansionTeamOf
chosen
Indicates that an organization or team was originally established as a new expansion unit of another existing organization or league.
-
B.
foundedFranchise
Indicates that an entity established or created a particular franchise.
-
C.
foundedAsFranchiseYear
Indicates the year in which an entity was established specifically as a franchise.
-
D.
foundedAsAffiliatedTeamOf
Indicates that an organization or team was originally established as an affiliated or subordinate team of another entity.
-
E.
foundedAsMajorLeagueClub
Indicates that an organization or team was originally established as a major league club at the time of its founding.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e6338081908aa03ee3dcbe5f70 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.