Triple
T25578696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somerset Patriots ballpark |
E641179
|
entity |
| Predicate | isVenueType |
P115407
|
FINISHED |
| Object | open-air stadium |
—
|
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: open-air stadium | Statement: [Somerset Patriots ballpark, isVenueType, open-air stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVenueType Context triple: [Somerset Patriots ballpark, isVenueType, open-air stadium]
-
A.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
-
B.
isVenueWithin
Indicates that one venue is geographically located inside the boundaries or area of another place or region.
-
C.
refersToVenueType
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
D.
locatedInVenueType
Indicates that an entity is situated within or associated with a venue of a specific type (e.g., stadium, theater, restaurant).
-
E.
hostVenueInstanceOf
chosen
Indicates that a specific host venue is an instance or concrete realization of a more general venue type or category.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9329b8c819088fd2a63492c5c5a |
completed | May 2, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69f4684442248190afe7677e56363e7f |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 4:03 p.m.