Triple
T2438106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buffalo Bills–New York Jets rivalry |
E53208
|
entity |
| Predicate | hasHomeAndAwayFormat |
P39328
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Buffalo Bills–New York Jets rivalry, hasHomeAndAwayFormat, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeAndAwayFormat Context triple: [Buffalo Bills–New York Jets rivalry, hasHomeAndAwayFormat, true]
-
A.
isHomeFieldOf
Indicates that a particular location or venue serves as the primary home field or home ground for a specific team or organization.
-
B.
hasPlayOffs
Indicates that a competition, league, or season includes a playoff stage to determine final rankings or a champion.
-
C.
isDivisionalMatchup
Indicates that the two entities (typically teams) are competing against each other within the same division.
-
D.
hasInterconferenceGame
Indicates that there exists a game played between teams belonging to different conferences.
-
E.
playedHomeGamesFrom
Indicates the time period during which a team or player hosted their home games at a particular venue.
- 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.