Triple
T8790400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2023 NBA All-Star Game |
E209147
|
entity |
| Predicate | draftTiming |
P85401
|
FINISHED |
| Object | immediately before tipoff |
—
|
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: immediately before tipoff | Statement: [2023 NBA All-Star Game, draftTiming, immediately before tipoff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: draftTiming Context triple: [2023 NBA All-Star Game, draftTiming, immediately before tipoff]
-
A.
draftCompleted
Indicates that the creation or preparation of a draft version of something has been finished.
-
B.
draftingStarted
Indicates that the process of creating an initial version or draft of something has begun.
-
C.
draftStatus
Indicates the current stage or condition of an item within a drafting or revision process (e.g., whether it is in draft, under review, or finalized).
-
D.
draft
Indicates that one entity prepares an initial or preliminary version of something, typically a document, plan, or design, which may be revised later.
-
E.
draftOrSigning
Indicates a relationship where an entity is involved in either the drafting or the signing phase of a document, agreement, or formal instrument.
- 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f8d25f881908863d636fa57a8a2 |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:43 p.m.