Triple
T32858782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobby Grier |
E840451
|
entity |
| Predicate | homeTeamInNotableGame |
P175081
|
FINISHED |
| Object | Pittsburgh Panthers football |
—
|
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: Pittsburgh Panthers football | Statement: [Bobby Grier, homeTeamInNotableGame, Pittsburgh Panthers football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamInNotableGame Context triple: [Bobby Grier, homeTeamInNotableGame, Pittsburgh Panthers football]
-
A.
teamInNotableGame
Indicates that a team participated as one of the competitors in a game or match considered notable or significant.
-
B.
notablePlayerWinningTeam
Indicates that a particular notable player was a member of the team that won a given competition or game.
-
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.
dateOfNotableGame
Indicates the calendar date on which a particular notable game took place.
-
E.
notableWin
Indicates that one entity achieved a particularly significant or distinguished victory over another or in a specific event.
- F. None of above. chosen
Provenance (4 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ceb2b81c81909c1a186305a9d597 |
completed | May 3, 2026, 4:27 a.m. |
| PD | Predicate disambiguation | batch_69f6cc177b288190904f3f23cb856d8b |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cdf2745481908464aa322c30d5b0 |
completed | May 3, 2026, 4:24 a.m. |
Created at: May 1, 2026, 1:17 a.m.