Triple
T31418738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalamazoo Hornets |
E801473
|
entity |
| Predicate | homeVenueForTennis |
P45848
|
FINISHED |
| Object | Stowe 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: Stowe Stadium | Statement: [Kalamazoo Hornets, homeVenueForTennis, Stowe Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueForTennis Context triple: [Kalamazoo Hornets, homeVenueForTennis, Stowe Stadium]
-
A.
hasTennisCourt
chosen
Indicates that one entity possesses, includes, or provides access to a tennis court as part of its facilities or attributes.
-
B.
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.
-
C.
homeArenaForTournament
Indicates that an arena serves as the designated home venue for a particular tournament.
-
D.
homeFencingVenue
Indicates that a specified venue serves as the primary or regular location where an entity (such as a team or fencer) hosts its fencing activities or events.
-
E.
AustralianOpenVenueUntil
Indicates that a venue served as the location for the Australian Open tennis tournament up to (and including) a specified end time or year.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:46 p.m.