Triple
T25988633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XL Center as primary home for UConn hockey |
E646275
|
entity |
| Predicate | venueOwnerContext |
P73096
|
FINISHED |
| Object | State of Connecticut |
—
|
NE NERFINISHED |
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: State of Connecticut | Statement: [XL Center as primary home for UConn hockey, venueOwnerContext, State of Connecticut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venueOwnerContext Context triple: [XL Center as primary home for UConn hockey, venueOwnerContext, State of Connecticut]
-
A.
venueOwner
chosen
Indicates that one entity is the owner or proprietor responsible for a particular venue or event location.
-
B.
venueManaged
Indicates that one entity is responsible for operating, organizing, or overseeing the management of a particular venue.
-
C.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
D.
hostVenueInstanceOf
Indicates that a specific host venue is an instance or concrete realization of a more general venue type or category.
-
E.
hostsVenue
Indicates that an entity provides or manages a location where an event or activity takes 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60545933081908d733c7bc49009f1 |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:55 a.m.