Triple
T4422001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Kickoff Game |
E95121
|
entity |
| Predicate | primaryParticipantType |
P6384
|
FINISHED |
| Object | defending Super Bowl champion |
—
|
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: defending Super Bowl champion | Statement: [NFL Kickoff Game, primaryParticipantType, defending Super Bowl champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryParticipantType Context triple: [NFL Kickoff Game, primaryParticipantType, defending Super Bowl champion]
-
A.
participantType
chosen
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
B.
primaryPatron
Indicates that one entity serves as the main or chief supporter, sponsor, or benefactor of another entity.
-
C.
primaryUser
Indicates that the referenced user is the main or principal user associated with a given account, resource, or context.
-
D.
primaryMembers
Indicates that the related entities are the main or most important members within a larger group or organization.
-
E.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554a0e7c8190b704d00d07b1857d |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.