Triple
T21414643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern All-Stars |
E528267
|
entity |
| Predicate | allStarGameContext |
P3180
|
FINISHED |
| Object | midseason exhibition game |
—
|
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: midseason exhibition game | Statement: [Eastern All-Stars, allStarGameContext, midseason exhibition game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allStarGameContext Context triple: [Eastern All-Stars, allStarGameContext, midseason exhibition game]
-
A.
allStarGame
chosen
Indicates that an entity participated in, was selected for, or is otherwise associated with an All-Star Game event.
-
B.
allStarGameResult
Indicates the outcome or result associated with an All-Star Game event between the involved entities.
-
C.
allStarGameYear
Indicates the year in which an all-star game event took place or is associated with a given entity.
-
D.
allStarGameArena
Indicates the arena or venue where an All-Star Game is held.
-
E.
allStarGameSignificance
Indicates the importance or impact that participation or performance in an All-Star Game has within a given context (such as a player’s career, a season, or a league).
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b2032fe48190907b282e2fffa2bd |
completed | April 22, 2026, 11:33 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:45 p.m.