Triple
T25618217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Football Club |
E642215
|
entity |
| Predicate | hasHomeStateTeamStatus |
P101447
|
FINISHED |
| Object | Victorian club |
—
|
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: Victorian club | Statement: [Richmond Football Club, hasHomeStateTeamStatus, Victorian club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeStateTeamStatus Context triple: [Richmond Football Club, hasHomeStateTeamStatus, Victorian club]
-
A.
homeStateTeamStatus
chosen
Indicates the status or condition of a team in relation to its designated home state.
-
B.
ownedTeamHomeState
Indicates that the owning entity’s home or primary location is in the same state as the team’s home state.
-
C.
teamHomeState
Indicates that a team’s designated home location is within a particular state.
-
D.
hasTeamInState
Indicates that an organization or entity has at least one team located or operating within a specified state.
-
E.
hasHomeTeamType
Indicates that an entity has a specified classification or category for its home team (e.g., type or role of the home team in a competition).
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 21, 2026, 5:02 p.m.