Triple
T28014873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 Green Bay Packers season |
E707519
|
entity |
| Predicate | startingPunter |
P84730
|
FINISHED |
| Object | Corey Bojorquez |
—
|
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: Corey Bojorquez | Statement: [2021 Green Bay Packers season, startingPunter, Corey Bojorquez]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingPunter Context triple: [2021 Green Bay Packers season, startingPunter, Corey Bojorquez]
-
A.
punter
chosen
Indicates the relationship where a person performs the action of punting, i.e., kicking or propelling a ball (or similar object) by dropping it and striking it before it hits the ground.
-
B.
startingTackle
Indicates that an entity holds the primary (starting) role at the tackle position in a lineup or formation.
-
C.
startingKicker
Indicates that the specified player is the primary kicker who starts the game or a particular match situation for their team.
-
D.
startingCatcher
Indicates that the specified player is the primary catcher in the starting lineup for a game.
-
E.
hasStartingPlayer
Indicates that a specific player is designated as the one who begins or takes the first turn in a game or activity.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: April 27, 2026, 8:06 p.m.