Triple
T6830607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guasave |
E157126
|
entity |
| Predicate | sportVenueType |
P25287
|
FINISHED |
| Object | baseball 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: baseball stadium | Statement: [Guasave, sportVenueType, baseball stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportVenueType Context triple: [Guasave, sportVenueType, baseball stadium]
-
A.
sportsVenueFor
Indicates that a venue is used as the location or facility where a particular sport or sporting event takes place.
-
B.
hasSportsVenueType
chosen
Indicates that a sports venue is classified as being of a specific type or category (e.g., stadium, arena, court).
-
C.
typicalVenueStadium
Indicates that the usual or characteristic venue for the referenced activity, event, or entity is a stadium.
-
D.
sportsFacility
Indicates that one entity is a sports facility where sports or physical activities can take place for the other entity.
-
E.
sportsVenueLocatedIn
Indicates that a sports venue is geographically situated within a specified location or administrative area.
- 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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62820808190ad3c244893e88699 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.