Triple
T21600538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Antonio Riders |
E533025
|
entity |
| Predicate | seasonRecord1992 |
P21379
|
FINISHED |
| Object | 7–3 |
—
|
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: 7–3 | Statement: [San Antonio Riders, seasonRecord1992, 7–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonRecord1992 Context triple: [San Antonio Riders, seasonRecord1992, 7–3]
-
A.
teamIn1992–93Season
Indicates that an entity was a member of or participated as a team in the 1992–93 season of a particular competition or league.
-
B.
1992–93Points
Indicates the number of points associated with entities specifically for the 1992–93 season or period.
-
C.
regularSeasonRecord1972–73
Indicates the win-loss (and possibly tie) record a team achieved during the 1972–73 regular season.
-
D.
seasonRecord
chosen
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
-
E.
seasonRecordWins
Indicates the number of games a team has won during a specific season.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e12fdc8190ab6125ea8d294717 |
completed | April 27, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:32 p.m.