Triple
T33660683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1986 NFC Championship Game |
E862342
|
entity |
| Predicate | homeTeamLinebacker |
P16137
|
FINISHED |
| Object | Lawrence Taylor |
—
|
NE NERFINISHED |
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: Lawrence Taylor | Statement: [1986 NFC Championship Game, homeTeamLinebacker, Lawrence Taylor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamLinebacker Context triple: [1986 NFC Championship Game, homeTeamLinebacker, Lawrence Taylor]
-
A.
middleLinebacker
Indicates that one entity serves in the role of middle linebacker in relation to a football team, formation, or defensive alignment.
-
B.
linebackersCoach
Indicates that one entity serves as the linebackers coach (position coach responsible for linebackers) for another entity, typically a team or organization.
-
C.
opponentDefensiveLine
Indicates the defensive line formed by the opposing side in a competitive or adversarial context.
-
D.
notableLinebacker
chosen
Indicates that the subject is a linebacker who is particularly prominent, distinguished, or well-recognized in that role.
-
E.
primaryDefensiveLine
Indicates the main line of defense that first engages or protects against an opposing force or threat.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:42 a.m.