Triple
T9848511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salt Lake Stallions |
E239403
|
entity |
| Predicate | playedRegularSeasonGames |
P30652
|
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: [Salt Lake Stallions, playedRegularSeasonGames, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedRegularSeasonGames Context triple: [Salt Lake Stallions, playedRegularSeasonGames, true]
-
A.
playedRegularSeasonGamesIn
chosen
Indicates that an athlete participated in one or more regular-season games for a specified team or league.
-
B.
regularSeasonGamesPlayed
Indicates the number of games an entity participated in during the regular season of a competition or league.
-
C.
playedPreseasonGames
Indicates that an entity participated in preseason games, typically before the official competitive season begins.
-
D.
hasRegularSeasonGamesAgainst
Indicates that one team or participant plays scheduled, recurring competitive games against another during the regular season.
-
E.
featuresRegularSeasonGames
Indicates that the subject includes or hosts games that are part of a standard, scheduled regular season competition.
- 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_69ca84e4fdc08190a624425bcef98665 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb371894c8190971ba497a2801521 |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:34 p.m.