Triple
T31673284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Eaton |
E808329
|
entity |
| Predicate | seasonOfBlocksRecord |
P33207
|
FINISHED |
| Object | 1984-85 NBA season |
—
|
NE NERFINISHED |
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: 1984-85 NBA season | Statement: [Mark Eaton, seasonOfBlocksRecord, 1984-85 NBA season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonOfBlocksRecord Context triple: [Mark Eaton, seasonOfBlocksRecord, 1984-85 NBA season]
-
A.
recordSetInSeason
chosen
Indicates that a particular record or achievement was set during a specified sports season.
-
B.
seasonCreated
Indicates that a particular season (of a show, competition, or series) was created or produced by a specific entity.
-
C.
seasonNumber
Indicates the ordinal position of a season within a series or sequence of seasons.
-
D.
seasonOrEdition
Indicates that one entity is a particular season or edition of another, such as a specific installment within a series or recurring event.
-
E.
seasonSequence
Indicates the ordered succession relationship between seasons, specifying which season follows or precedes another in a temporal sequence.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 30, 2026, 11:02 p.m.