Triple
T34100221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Ten–Pac-8 Rose Bowl agreement |
E874546
|
entity |
| Predicate | primaryParticipantsRole |
P6384
|
FINISHED |
| Object | conference champions |
—
|
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: conference champions | Statement: [Big Ten–Pac-8 Rose Bowl agreement, primaryParticipantsRole, conference champions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryParticipantsRole Context triple: [Big Ten–Pac-8 Rose Bowl agreement, primaryParticipantsRole, conference champions]
-
A.
primaryParticipant
Indicates that an entity plays the main or most central role in a given event, activity, or relationship.
-
B.
primaryUsersRole
Indicates the role that a primary user holds in relation to a given resource, system, or context.
-
C.
primaryRoleFor
Indicates that one entity serves as the main or most important role or function for another entity.
-
D.
primaryPeople
Indicates that the referenced people are the main or most important individuals associated with a given entity, event, or context.
-
E.
participantType
chosen
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:53 a.m.