Triple
T29826863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle for the Fremont Cannon |
E757402
|
entity |
| Predicate | homeVenuesInclude |
P98385
|
FINISHED |
| Object | Mackay Stadium |
—
|
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: Mackay Stadium | Statement: [Battle for the Fremont Cannon, homeVenuesInclude, Mackay Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenuesInclude Context triple: [Battle for the Fremont Cannon, homeVenuesInclude, Mackay Stadium]
-
A.
homeVenueIncludes
chosen
Indicates that a specified venue is part of, contained within, or used as a home location by another entity.
-
B.
homeMeetsVenue
Indicates that a home team plays its scheduled match at a specified venue.
-
C.
usesHomeVenuesFor
Indicates that an entity regularly holds its home events or activities at the specified venues.
-
D.
home venue type
Indicates the kind or category of place that serves as the primary location where an entity regularly hosts its events or activities.
-
E.
homeVenueFocus
Indicates a primary or central emphasis on a particular venue as the main location associated with an entity’s activities or presence.
- 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67598dff081908ff0ec79a48b55ec |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:32 p.m.