Triple
T36842043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenyan Drake |
E910432
|
entity |
| Predicate | opponentTeamInNotablePlay |
P48918
|
FINISHED |
| Object | New England Patriots |
—
|
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: New England Patriots | Statement: [Kenyan Drake, opponentTeamInNotablePlay, New England Patriots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentTeamInNotablePlay Context triple: [Kenyan Drake, opponentTeamInNotablePlay, New England Patriots]
-
A.
opposingTeamInNotableEvent
chosen
Indicates that one entity served as the opposing team of another entity in a specific notable event or competition.
-
B.
notableRivalTeam
Indicates that one team is recognized as a significant or well-known rival of another team.
-
C.
notablePlayerAwayTeam
Indicates that a specific player is recognized as a notable or standout member of the away team in a given game or event.
-
D.
teamInNotableGame
Indicates that a team participated as one of the competitors in a game or match considered notable or significant.
-
E.
notablePlayerWinningTeam
Indicates that a particular notable player was a member of the team that won a given competition or game.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.