Triple
T5993145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Knicks–Brooklyn Nets rivalry |
E133399
|
entity |
| Predicate | typeOfGame |
P8300
|
FINISHED |
| Object | regular season games |
—
|
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: regular season games | Statement: [New York Knicks–Brooklyn Nets rivalry, typeOfGame, regular season games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfGame Context triple: [New York Knicks–Brooklyn Nets rivalry, typeOfGame, regular season games]
-
A.
ballGameType
Indicates the specific kind or category of ball game associated with an event or activity.
-
B.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
C.
hasGameType
chosen
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
D.
includesGameType
Indicates that one entity contains or supports a particular type or category of game.
-
E.
traditionalGame
Indicates that the relationship involves playing, practicing, or being associated with a game that is rooted in longstanding cultural or historical traditions.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e9189908190abc9c742b38dfabc |
completed | March 22, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.