Triple
T16308272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oakland Invaders |
E395975
|
entity |
| Predicate | seasonRecord1983 |
P21379
|
FINISHED |
| Object | 9–9 |
—
|
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: 9–9 | Statement: [Oakland Invaders, seasonRecord1983, 9–9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonRecord1983 Context triple: [Oakland Invaders, seasonRecord1983, 9–9]
-
A.
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).
-
B.
bestRegularSeasonRecordYear
Indicates the year in which an entity achieved its best regular-season record compared to all its other seasons.
-
C.
regularSeasonRecord1967–68
Indicates the win-loss (and possibly tie) performance of a team during the 1967–68 regular season.
-
D.
bestSeasonRecord
Indicates that one entity holds the best (most successful) season performance record among a set of entities, typically in a competitive or statistical context.
-
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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e288d776808190a7c9918477f07216 |
completed | April 17, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.