Triple
T8811345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DeSean Jackson scored a walk-off punt return touchdown |
E209668
|
entity |
| Predicate | returnDirection |
P84735
|
FINISHED |
| Object | right sideline |
—
|
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: right sideline | Statement: [DeSean Jackson scored a walk-off punt return touchdown, returnDirection, right sideline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnDirection Context triple: [DeSean Jackson scored a walk-off punt return touchdown, returnDirection, right sideline]
-
A.
returnedVia
Indicates that something was sent back or responded to through a specified medium, channel, or method.
-
B.
returnsTo
Indicates that an entity goes back to a previous location, state, or entity it was associated with before.
-
C.
returnService
Indicates a relationship where a service that was previously provided is being sent back, reversed, or requested to be undone or refunded.
-
D.
returns
Indicates that one entity gives or sends something back to another entity, often as a result or outcome of a process or action.
-
E.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
- 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_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. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:45 p.m.