Triple
T4540495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogers Stadium Limited Partnership |
E107515
|
entity |
| Predicate | managesVenueType |
P43750
|
FINISHED |
| Object | multi-purpose 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: multi-purpose stadium | Statement: [Rogers Stadium Limited Partnership, managesVenueType, multi-purpose stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesVenueType Context triple: [Rogers Stadium Limited Partnership, managesVenueType, multi-purpose stadium]
-
A.
operatesVenue
Indicates that one entity manages and runs the day-to-day operations of a particular venue.
-
B.
refersToVenueType
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
C.
recordSettingVenueFor
Indicates the venue or location where a particular record (such as a performance, achievement, or measurement) was set.
-
D.
venueTypeOperated
chosen
Indicates that an entity operates or manages a venue of a specified type.
-
E.
servesVenue
Indicates that an entity provides services or functions in support of a particular venue.
- 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_69bd43f922788190b7edfa294e39b178 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57bb5c0c819092ebb2dd3310f5f8 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:04 p.m.