Triple
T33233856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1981 AFC Championship Game |
E850773
|
entity |
| Predicate | berthAwardedTo |
P43563
|
FINISHED |
| Object | Super Bowl XVI |
—
|
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: Super Bowl XVI | Statement: [1981 AFC Championship Game, berthAwardedTo, Super Bowl XVI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: berthAwardedTo Context triple: [1981 AFC Championship Game, berthAwardedTo, Super Bowl XVI]
-
A.
determinedBerthIn
Indicates that an entity has been assigned or allocated to a specific berth or docking position.
-
B.
earnedBerthIn
chosen
Indicates that one entity has qualified for or secured a place in a particular event, competition, or stage as a result of its performance or achievement.
-
C.
berthType
Indicates the specific kind or category of berth associated with an entity, such as the type of sleeping or docking space provided.
-
D.
mooredAt
Indicates that one object, typically a vessel or floating structure, is secured or anchored at a specific location or facility.
-
E.
previousBerth
Indicates that one berth directly precedes another in a defined ordering or sequence.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:31 a.m.