Triple
T28391791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fremont Cannon |
E719172
|
entity |
| Predicate | locationWhenUNLVHolds |
P17057
|
FINISHED |
| Object | University of Nevada, Las Vegas campus |
—
|
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: University of Nevada, Las Vegas campus | Statement: [Fremont Cannon, locationWhenUNLVHolds, University of Nevada, Las Vegas campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationWhenUNLVHolds Context triple: [Fremont Cannon, locationWhenUNLVHolds, University of Nevada, Las Vegas campus]
-
A.
homeVenueLSU
Indicates that the specified venue serves as the home location or home field for LSU.
-
B.
FinalFourVenue
Indicates that a venue is the designated location where the Final Four round of a tournament is held.
-
C.
hasCampusOn
Indicates that an institution or organization maintains a campus located on a specified geographic area or site.
-
D.
homeVenueForVirginiaTech
Indicates that a venue serves as the primary home location where Virginia Tech hosts its events or activities.
-
E.
typicallyHeldIn
chosen
Indicates that an event, activity, or process most commonly or usually takes place within a particular location, venue, or context.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69ff6ef0d61c81909162d37c15a1a3c3 |
completed | May 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ff6c6a58e08190921317062cd9d489 |
completed | May 9, 2026, 5:18 p.m. |
Created at: April 28, 2026, 1:14 a.m.