Triple
T35981210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silvertails |
E1040566
|
entity |
| Predicate | homeGroundOfReferencedClub |
P164581
|
FINISHED |
| Object | Brookvale Oval |
—
|
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: Brookvale Oval | Statement: [Silvertails, homeGroundOfReferencedClub, Brookvale Oval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGroundOfReferencedClub Context triple: [Silvertails, homeGroundOfReferencedClub, Brookvale Oval]
-
A.
homeGroundOfAssociatedClub
chosen
Indicates that a particular venue or ground serves as the designated home location for an associated sports club.
-
B.
hometownClubOf
Indicates that a club is recognized as the hometown or local club associated with a particular person or entity.
-
C.
homeGroundAlternateName
Indicates that an alternative or secondary name is used to refer to a particular home ground.
-
D.
homeGroundTown
Indicates that a particular town is recognized as the home ground or primary hosting location for a team, organization, or entity.
-
E.
homeStadiumAlsoKnownAs
Indicates that an alternative or alias name is used for a stadium that serves as a team's home venue.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.