Triple
T22419385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Conference playoff elimination games |
E554204
|
entity |
| Predicate | hasPossibleGameNumber |
P102007
|
FINISHED |
| Object | Game 4 |
—
|
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 4 | Statement: [Eastern Conference playoff elimination games, hasPossibleGameNumber, Game 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPossibleGameNumber Context triple: [Eastern Conference playoff elimination games, hasPossibleGameNumber, Game 4]
-
A.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
B.
winningGameNumber
Indicates the specific game number in a series or sequence that results in a win for a given participant or side.
-
C.
hasGamesAt
Indicates that a particular location, venue, or platform hosts or offers one or more games.
-
D.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
E.
associatedWithGameNumber
chosen
Indicates a relationship where something is linked or tied to a specific game identified by its number.
- 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_69e11e4e6ce8819085a1e06d886bf21c |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15948dcdc81909d0a792c4498fa70 |
completed | April 29, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.