Triple
T7095562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratt & Whitney Stadium at Rentschler Field |
E165314
|
entity |
| Predicate | hasEndZones |
P6793
|
FINISHED |
| Object | painted with UConn branding |
—
|
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: painted with UConn branding | Statement: [Pratt & Whitney Stadium at Rentschler Field, hasEndZones, painted with UConn branding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndZones Context triple: [Pratt & Whitney Stadium at Rentschler Field, hasEndZones, painted with UConn branding]
-
A.
hasEndZonesColor
Indicates that the specified color is the one used for the end zones associated with an entity.
-
B.
hasEndZoneSeating
Indicates that seating is available in the end zone area of a sports venue.
-
C.
numberOfZones
Indicates the quantity of distinct zones associated with or contained by a given entity.
-
D.
hasZone
chosen
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
E.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
- 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5530f2081908ac969ddfa7e9b5a |
completed | March 27, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.