Triple
T3726844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bj league 2007–08 |
E81769
|
entity |
| Predicate | finalsType |
P30656
|
FINISHED |
| Object | playoff finals |
—
|
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: playoff finals | Statement: [bj league 2007–08, finalsType, playoff finals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalsType Context triple: [bj league 2007–08, finalsType, playoff finals]
-
A.
finalMatchType
chosen
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
B.
finalsLocation
Indicates the place where the final stage or concluding event of something (such as a competition or process) takes place.
-
C.
nextFinals
Indicates that one event, match, or stage directly follows another as the subsequent or upcoming finals in a sequence.
-
D.
finalists
Indicates that the related entities have advanced to the final round or stage of a competition, selection process, or evaluation.
-
E.
finalLeague
Indicates the league or competition in which an entity ultimately ends up or is officially classified, typically after all stages or transitions are complete.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf7a6908190bd0c3bb5c55ab9ee |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.