Triple
T5702497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaxico Burress |
E125696
|
entity |
| Predicate | scored |
P10576
|
FINISHED |
| Object | game-winning touchdown in Super Bowl XLII |
—
|
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: game-winning touchdown in Super Bowl XLII | Statement: [Plaxico Burress, scored, game-winning touchdown in Super Bowl XLII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scored Context triple: [Plaxico Burress, scored, game-winning touchdown in Super Bowl XLII]
-
A.
scoredFor
Indicates that one entity achieved points or a score on behalf of another entity, such as a player scoring for a team.
-
B.
scoring
chosen
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
-
C.
scoredBy
Indicates that a particular score, point, or result was achieved or obtained by a specific entity.
-
D.
coScoredWith
Indicates that two or more entities received the same score or were evaluated with an identical scoring outcome in a shared context.
-
E.
hasScoredFor
Indicates that one entity has scored points, goals, or similar achievements on behalf of another entity, such as a team, organization, or side.
- 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0245581988190a819b8137533ed31 |
completed | March 22, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:45 p.m.