Triple
T14309310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brunswick Street Oval |
E354780
|
entity |
| Predicate | usedAsHomeGroundFrom |
P89880
|
FINISHED |
| Object | 1897 |
—
|
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: 1897 | Statement: [Brunswick Street Oval, usedAsHomeGroundFrom, 1897]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsHomeGroundFrom Context triple: [Brunswick Street Oval, usedAsHomeGroundFrom, 1897]
-
A.
usedAsHomeCourtOf
Indicates that a particular venue or location serves as the primary home court where a team or individual regularly hosts its games or matches.
-
B.
usedAsHomeArenaFrom
chosen
Indicates that a particular venue served as the home arena for an entity (such as a team) starting from a specified point in time.
-
C.
previousHomeFieldUse
Indicates that one entity was formerly used as the home field or primary venue for another entity before a later change.
-
D.
primaryHomeGroundNot
Indicates that the specified location is explicitly not the entity’s primary home ground.
-
E.
homeGroundUsedFor
Indicates that a particular venue or stadium is used as the designated home ground for a team, club, or organization.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b26da48190a96e2f60ace51335 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.