Triple
T29403641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Wayne TinCaps |
E745722
|
entity |
| Predicate | homeVenueOpenedAsTinCapsHome |
P40950
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Fort Wayne TinCaps, homeVenueOpenedAsTinCapsHome, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueOpenedAsTinCapsHome Context triple: [Fort Wayne TinCaps, homeVenueOpenedAsTinCapsHome, 2009]
-
A.
homeVenueOpened
chosen
Indicates that a venue has officially begun operating as the designated home location for a particular team or organization.
-
B.
earlyHomeVenueFor
Indicates that one entity served as the primary home venue for another entity during an early or initial period of its existence or activity.
-
C.
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.
-
D.
homeVenueTown
Indicates the town or municipality where an entity’s primary or home venue is located.
-
E.
homeVenueCovered
Indicates that the primary or home venue associated with an entity is included within the scope of a specified coverage, protection, or service.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a3143948190aeff396f02748fb8 |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:52 p.m.