Triple
T2438081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buffalo Bills–New York Jets rivalry |
E53208
|
entity |
| Predicate | beganPlayBetweenTeams |
P39323
|
FINISHED |
| Object | 1960 |
—
|
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: 1960 | Statement: [Buffalo Bills–New York Jets rivalry, beganPlayBetweenTeams, 1960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganPlayBetweenTeams Context triple: [Buffalo Bills–New York Jets rivalry, beganPlayBetweenTeams, 1960]
-
A.
beganCompetition
Indicates that an entity initiated or started participating in a competitive event or contest involving others.
-
B.
hasNumberOfTeams
Indicates the quantity of teams associated with or contained by a given entity.
-
C.
openingMatch
Indicates that one entity serves as the initial or first match, game, or contest in a series, event, or competition involving another entity.
-
D.
advancesTeamsTo
Indicates that one entity causes or marks the progression of one or more teams to a subsequent stage, level, or round in a process or competition.
-
E.
teamPlayedFor
Indicates that a person was a member of and played for a particular sports team.
- 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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
| PDg | Predicate description generation | batch_69abcebe7dd08190b197a2a0e78787e3 |
completed | March 7, 2026, 7:07 a.m. |
Created at: March 6, 2026, 9:43 p.m.