Triple
T14040711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonio Brown |
E337836
|
entity |
| Predicate | proFootballReferenceID |
P112597
|
FINISHED |
| Object | BrowAn04 |
—
|
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: BrowAn04 | Statement: [Antonio Brown, proFootballReferenceID, BrowAn04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proFootballReferenceID Context triple: [Antonio Brown, proFootballReferenceID, BrowAn04]
-
A.
nflRecord
Indicates the win-loss-tie performance record a team or individual has accumulated in NFL competition.
-
B.
NFLTouchdownPasses
Indicates that a player successfully throws a pass that results in a touchdown being scored in an NFL game.
-
C.
nflProBowls
Indicates the number of times a player has been selected to participate in the NFL Pro Bowl all-star game.
-
D.
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).
-
E.
playedAmericanFootball
Indicates that one entity participated in playing American football, either professionally, collegiately, or at another organized level, during some period of time.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de311814e48190adb637e1c97c0658 |
completed | April 14, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:20 p.m.