Triple
T27882698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1976 Rose Bowl |
E705134
|
entity |
| Predicate | uclaRankAP |
P55830
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [1976 Rose Bowl, uclaRankAP, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uclaRankAP Context triple: [1976 Rose Bowl, uclaRankAP, 11]
-
A.
UCLARanking
chosen
Indicates a ranking relationship that orders entities based on their position or standing within the context of UCLA (e.g., programs, departments, or individuals associated with the university).
-
B.
UCLACenter
Indicates that an entity serves as a center or hub associated with UCLA (University of California, Los Angeles).
-
C.
universityRankContext
Indicates the contextual framework or criteria under which a university’s rank or ranking position is determined or interpreted.
-
D.
rankInCalifornia
Indicates the position or standing of an entity within a ranking specific to California.
-
E.
apexInstitution
Indicates that an institution holds the highest or ultimate authority or status within a given organizational, administrative, or hierarchical structure.
- 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_69f639aeb1fc81908fab01d2a548512a |
completed | May 2, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69f6318be69481909d1bcf29b7b60eb2 |
completed | May 2, 2026, 5:17 p.m. |
Created at: April 27, 2026, 6:31 p.m.