Triple
T4376361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCLA Bruins football |
E99015
|
entity |
| Predicate | homeFieldSince |
P56462
|
FINISHED |
| Object | Rose Bowl 1982 |
—
|
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: Rose Bowl 1982 | Statement: [UCLA Bruins football, homeFieldSince, Rose Bowl 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeFieldSince Context triple: [UCLA Bruins football, homeFieldSince, Rose Bowl 1982]
-
A.
homeTeamSince
Indicates the point in time from which a particular team has been designated as the home team for a given context or venue.
-
B.
previousHomeFieldYears
Indicates the years during which a particular location previously served as the home field for an entity (such as a team or organization).
-
C.
homeFieldLocation
Indicates the location where an entity’s primary or home field, venue, or playing ground is situated.
-
D.
homeFieldNamedAfter
Indicates that one entity’s home playing field bears the name of another entity.
-
E.
isHomeFieldOf
Indicates that a particular location or venue serves as the primary home field or home ground for a specific team or organization.
- 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3523d4e888190b4367ed6aa17d463 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b35034cd248190bae09e9d090e13ec |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:18 p.m.