Triple
T24541063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drew Bledsoe |
E607091
|
entity |
| Predicate | injuryOccurredWhilePlayingFor |
P156658
|
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: [Drew Bledsoe, injuryOccurredWhilePlayingFor, New England Patriots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: injuryOccurredWhilePlayingFor Context triple: [Drew Bledsoe, injuryOccurredWhilePlayingFor, New England Patriots]
-
A.
injuredIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
-
B.
injuryInvolvedPlayer
Indicates that a specific player is involved in, affected by, or associated with a particular injury event.
-
C.
battedForTeamAtTimeOfInjury
Indicates that a player was batting for a specific team at the time the injury occurred.
-
D.
injuryOpponentTeam
Indicates that one team causes an injury to a member of the opposing team during a contest or interaction.
-
E.
wasSidelinedBy
Indicates that one entity was removed from an active or central role by another entity, typically in favor of others or to reduce its influence or participation.
- 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:26 a.m.