Triple
T25254456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond (AFLW) |
E633128
|
entity |
| Predicate | homeStateLeagueRegion |
P158432
|
FINISHED |
| Object | Victoria |
—
|
NE NERFINISHED |
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: Victoria | Statement: [Richmond (AFLW), homeStateLeagueRegion, Victoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStateLeagueRegion Context triple: [Richmond (AFLW), homeStateLeagueRegion, Victoria]
-
A.
homeRegionLeague
Indicates that a league is the primary or native regional competition associated with an entity (such as a team or club).
-
B.
homeStateTeam
Indicates that a sports team is based in, or represents, the home state of a given person or entity.
-
C.
homeStateFanBase
Indicates that a fan base is primarily located in or strongly associated with the same state as the team, person, or entity it supports.
-
D.
homeStateTeamOf
Indicates that one team is the designated home-state team associated with a particular person, organization, or region.
-
E.
homeStateCompetition
Indicates a competitive event or rivalry that takes place within, or is specifically associated with, an entity’s home state.
- F. None of above. chosen
Provenance (4 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4808f350881908ebf53f883f5e5b0 |
completed | May 1, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:13 p.m.