Triple
T5623849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Conference All-Stars |
E147671
|
entity |
| Predicate | gameStatus |
P30623
|
FINISHED |
| Object | non-regular-season exhibition |
—
|
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: non-regular-season exhibition | Statement: [Western Conference All-Stars, gameStatus, non-regular-season exhibition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameStatus Context triple: [Western Conference All-Stars, gameStatus, non-regular-season exhibition]
-
A.
gameState
chosen
Indicates the current status or condition of a game at a particular point in time, including relevant rules, progress, and contextual information.
-
B.
game5Status
Indicates the current state or outcome of the fifth game in a series or sequence of games.
-
C.
playerStatus
Indicates the current state or condition of a player within a game or system, such as their activity, health, or participation status.
-
D.
game4Winner
Indicates which participant or side is the winner of the fourth game in a series or match.
-
E.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02214b4948190b71a9f59499092f6 |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.