Triple
T26389172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2023 NBA Finals |
E663364
|
entity |
| Predicate | seriesClinchingDate |
P168916
|
FINISHED |
| Object | 2023-06-12 |
—
|
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: 2023-06-12 | Statement: [2023 NBA Finals, seriesClinchingDate, 2023-06-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesClinchingDate Context triple: [2023 NBA Finals, seriesClinchingDate, 2023-06-12]
-
A.
seriesClinchingShotBy
Indicates that a particular shot or play was made by an entity and directly resulted in clinching or deciding the outcome of a series.
-
B.
seriesInception
Indicates the event or point in time at which a series is first created, launched, or begins.
-
C.
seriesPremiereOf
Indicates that one creative work (typically an episode) is the first-ever installment that begins a television or similar serialized series.
-
D.
seriesOf
Indicates that one entity is a sequence or ordered set of related items, events, or parts that collectively form or belong to another entity.
-
E.
seriesYear
Indicates the year in which a series (such as a TV show, book series, or event series) is released, set, or primarily associated.
- F. None of above. chosen
Provenance (4 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 26, 2026, 11:24 p.m.