Triple
T19840734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2001–02 Sacramento Kings season |
E476718
|
entity |
| Predicate | conferenceFinalsResult |
P112197
|
FINISHED |
| Object | 4–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: 4–3 | Statement: [2001–02 Sacramento Kings season, conferenceFinalsResult, 4–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceFinalsResult Context triple: [2001–02 Sacramento Kings season, conferenceFinalsResult, 4–3]
-
A.
conferenceFinalsSeriesResult
chosen
Indicates the outcome of a conference finals playoff series between two competitors, including which side won and by what series score.
-
B.
finalMatches
Indicates that two or more items correspond exactly in their final or completed form, satisfying all criteria for being considered the same at the end state.
-
C.
finalOfficialMatch
Indicates that a given match is the last officially recognized contest or game in a defined series, season, tournament, or career.
-
D.
semifinalResult
Indicates the outcome or score of a semifinal-stage contest or match between competitors.
-
E.
finalMatchDecidedBy
Indicates that the outcome of a final match is determined by a specific method, event, or deciding factor.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6580576748190b85e234b01209ae7 |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.