Triple
T9130202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNLV Rebels baseball |
E219065
|
entity |
| Predicate | homeVenueUse |
P41695
|
FINISHED |
| Object | on-campus 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: on-campus stadium | Statement: [UNLV Rebels baseball, homeVenueUse, on-campus stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueUse Context triple: [UNLV Rebels baseball, homeVenueUse, on-campus stadium]
-
A.
homeVenueAlsoUsedBy
Indicates that the venue serving as a home location for one entity is also used as a venue by another entity.
-
B.
home venue type
chosen
Indicates the kind or category of place that serves as the primary location where an entity regularly hosts its events or activities.
-
C.
homeVenueOwned
Indicates that the specified home venue is legally owned or possessed by the associated entity.
-
D.
homeVenueFocus
Indicates a primary or central emphasis on a particular venue as the main location associated with an entity’s activities or presence.
-
E.
usesVenues
Indicates that one entity makes use of or operates within specific venues or locations to carry out its activities or services.
- 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8cdafb48190be5e62b15779d771 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.