Triple
T32858781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobby Grier |
E840451
|
entity |
| Predicate | opponentTeamInNotableGame |
P48918
|
FINISHED |
| Object | Georgia Tech Yellow Jackets 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: Georgia Tech Yellow Jackets football | Statement: [Bobby Grier, opponentTeamInNotableGame, Georgia Tech Yellow Jackets football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentTeamInNotableGame Context triple: [Bobby Grier, opponentTeamInNotableGame, Georgia Tech Yellow Jackets football]
-
A.
teamInNotableGame
Indicates that a team participated as one of the competitors in a game or match considered notable or significant.
-
B.
notableRivalTeam
Indicates that one team is recognized as a significant or well-known rival of another team.
-
C.
opposingTeamInNotableEvent
chosen
Indicates that one entity served as the opposing team of another entity in a specific notable event or competition.
-
D.
homeTeamInNotableGame
Indicates that an entity serves as the home team in a specific notable or significant game or match.
-
E.
notableRivalOpponent
Indicates that one entity is a particularly significant or well-known rival or opponent of another entity.
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:17 a.m.