Triple
T13571333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-Mobile Home Run Derby |
E324167
|
entity |
| Predicate | usesVenueArea |
P95650
|
FINISHED |
| Object | entire outfield stands |
—
|
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: entire outfield stands | Statement: [T-Mobile Home Run Derby, usesVenueArea, entire outfield stands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVenueArea Context triple: [T-Mobile Home Run Derby, usesVenueArea, entire outfield stands]
-
A.
usesVenues
Indicates that one entity makes use of or operates within specific venues or locations to carry out its activities or services.
-
B.
isVenueWithin
Indicates that one venue is geographically located inside the boundaries or area of another place or region.
-
C.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
-
D.
venueArea
Indicates the physical size or spatial extent of a venue, typically measured in units such as square meters or square feet.
-
E.
hostedEventAreaFor
chosen
Indicates that a particular area or location served as the venue or physical space where an event was hosted or took place.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00f5b8881908617f42d227ed137 |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.