Triple
T32379089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ursinus Bears |
E827363
|
entity |
| Predicate | homeVenueForFieldHockey |
P173999
|
FINISHED |
| Object | Eleanor Frost Snell Alumnae Field |
—
|
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: Eleanor Frost Snell Alumnae Field | Statement: [Ursinus Bears, homeVenueForFieldHockey, Eleanor Frost Snell Alumnae Field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueForFieldHockey Context triple: [Ursinus Bears, homeVenueForFieldHockey, Eleanor Frost Snell Alumnae Field]
-
A.
homeVenueLacrosse
Indicates that a specified venue serves as the designated home location where a particular lacrosse team hosts its home games or matches.
-
B.
mainIceHockeyVenue
Indicates that a location serves as the primary venue where a team or organization regularly plays its ice hockey games.
-
C.
gameVenue
Indicates the location or facility where a game or match is held.
-
D.
homeFencingVenue
Indicates that a specified venue serves as the primary or regular location where an entity (such as a team or fencer) hosts its fencing activities or events.
-
E.
homeArenaHockey
Indicates that a particular arena serves as the designated home venue for a specific hockey team.
- F. None of above. chosen
Provenance (4 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c133d2548190bd25b6f347038f63 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:51 a.m.