Triple
T16330820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dez Bryant |
E396544
|
entity |
| Predicate | notablePlayStyle |
P3775
|
FINISHED |
| Object | physical contested-catch receiver |
—
|
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: physical contested-catch receiver | Statement: [Dez Bryant, notablePlayStyle, physical contested-catch receiver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayStyle Context triple: [Dez Bryant, notablePlayStyle, physical contested-catch receiver]
-
A.
styleOfPlay
chosen
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
B.
notablePlay
Indicates that a particular play is especially famous, significant, or noteworthy in relation to the entity it is associated with.
-
C.
notablePlayType
Indicates that a particular type or category of play is especially significant or characteristic for the subject.
-
D.
notableLeagueCharacteristic
Indicates that a particular characteristic is especially prominent or defining for a given league.
-
E.
notableWorkStyle
Indicates a stylistic characteristic or distinctive manner associated with a notable work created by the subject.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4dfd9688190a749e48ebc055baf |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.