Triple
T13845577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Hadl |
E332794
|
entity |
| Predicate | NFLIdentifier |
P63232
|
FINISHED |
| Object | HAD415290 |
—
|
LITERAL FINISHED |
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: HAD415290 | Statement: [John Hadl, NFLIdentifier, HAD415290]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NFLIdentifier Context triple: [John Hadl, NFLIdentifier, HAD415290]
-
A.
nflId
chosen
Indicates a unique identifier assigned to an NFL player or entity within the dataset, used to distinguish it from all others.
-
B.
NFLTeam
Indicates a relationship where an entity is identified as a professional American football team that competes in the National Football League.
-
C.
NFLStatus
Indicates the current professional status or condition of an entity within the context of the National Football League (e.g., active, injured, retired, free agent).
-
D.
proBowlTeam
Indicates that a player was selected to and participated on a specific team in the Pro Bowl all-star game.
-
E.
roleAtTampaBayBuccaneers
Indicates that an entity holds or held a specific role or position within the Tampa Bay Buccaneers organization.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02b1a25c8190a9f85ba43c421188 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.