Triple
T27882688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1976 Rose Bowl |
E705134
|
entity |
| Predicate | conferenceOfUCLA |
P3307
|
FINISHED |
| Object | Pacific-8 Conference |
—
|
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: Pacific-8 Conference | Statement: [1976 Rose Bowl, conferenceOfUCLA, Pacific-8 Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceOfUCLA Context triple: [1976 Rose Bowl, conferenceOfUCLA, Pacific-8 Conference]
-
A.
UCLACenter
Indicates that an entity serves as a center or hub associated with UCLA (University of California, Los Angeles).
-
B.
conferenceInCollege
Indicates that a conference is being held at, hosted by, or located within a particular college.
-
C.
conferenceSince
Indicates that a conference-related relationship or interaction between entities has been in effect continuously since a specified point in time.
-
D.
conference1
chosen
Indicates a relationship where an entity is associated with, participates in, or is characterized as a specific conference event or instance.
-
E.
otherConference
Indicates that one conference is distinct from and not the same as another conference.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 6:31 p.m.