Triple
T8811350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DeSean Jackson scored a walk-off punt return touchdown |
E209668
|
entity |
| Predicate | ballCarrierPosition |
P80655
|
FINISHED |
| Object | wide 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: wide receiver | Statement: [DeSean Jackson scored a walk-off punt return touchdown, ballCarrierPosition, wide receiver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballCarrierPosition Context triple: [DeSean Jackson scored a walk-off punt return touchdown, ballCarrierPosition, wide receiver]
-
A.
ballLocation
Indicates the spatial position or coordinates where a ball is currently located.
-
B.
bearerPosition
chosen
Indicates the spatial or positional relationship of a bearer (holder or carrier) relative to the item or entity it bears.
-
C.
playingPosition
Indicates the specific role or position an individual occupies while participating in a game or sport.
-
D.
ballPlacement
Indicates the spatial positioning or arrangement of a ball relative to a reference point, object, or area.
-
E.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fed18f8819087b0282bf8c4208c |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.