Triple
T11815654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Western Sydney Giants |
E280992
|
entity |
| Predicate | homeCityTeamStatus |
P101448
|
FINISHED |
| Object | second AFL club in Sydney |
—
|
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: second AFL club in Sydney | Statement: [Greater Western Sydney Giants, homeCityTeamStatus, second AFL club in Sydney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCityTeamStatus Context triple: [Greater Western Sydney Giants, homeCityTeamStatus, second AFL club in Sydney]
-
A.
homeCityTeamOf
Indicates that one entity is the sports team based in and representing the home city of the other entity.
-
B.
teamCityOfFranchiseOwned
Indicates that a particular city serves as the home or base city for a sports franchise that is owned by a specified owner.
-
C.
homeStateTeamOf
Indicates that one team is the designated home-state team associated with a particular person, organization, or region.
-
D.
homeCityNHLReturn
Indicates that an NHL player has returned to play for a team based in or near their hometown or home city.
-
E.
teamLocation
Indicates that a team is based in, associated with, or operates from a particular geographic location.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a6574b7081908f7451d2bb233967 |
completed | April 10, 2026, 7:27 a.m. |
Created at: April 8, 2026, 9:42 p.m.