Triple
T22151721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scooch |
E547429
|
entity |
| Predicate | associatedWithSportVenueType |
P25287
|
FINISHED |
| Object | baseball stadiums |
—
|
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 stadiums | Statement: [Scooch, associatedWithSportVenueType, baseball stadiums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSportVenueType Context triple: [Scooch, associatedWithSportVenueType, baseball stadiums]
-
A.
hasSportsVenueType
chosen
Indicates that a sports venue is classified as being of a specific type or category (e.g., stadium, arena, court).
-
B.
hasAssociatedSportsVenue
Indicates that an entity is linked to a specific sports venue with which it is functionally or contextually associated.
-
C.
isPartOfSportsVenue
Indicates that one entity is a component, section, or area contained within a larger sports venue.
-
D.
venueAssociatedWith
Indicates that there is a relevant connection or linkage between an event, activity, or entity and a particular venue or location.
-
E.
associatedWithTeamSport
Indicates a relationship where an entity is connected to, involved in, or participates in a team-based sport.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f4b05c8190a824f55804f6d4d5 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.