Triple
T8948873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2024 NBA All-Star Game |
E213291
|
entity |
| Predicate | draftFormatUsed |
P86499
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [2024 NBA All-Star Game, draftFormatUsed, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: draftFormatUsed Context triple: [2024 NBA All-Star Game, draftFormatUsed, no]
-
A.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
B.
draftType
Indicates the specific category or kind of draft associated with an entity or document (e.g., initial, revised, or final draft).
-
C.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
-
D.
documentTypeUsed
Indicates that a particular type or category of document is employed or applied in a given context or activity.
-
E.
documentForm
Indicates the specific format or structural type in which a document is presented or recorded.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6709c7a48190ab503083a1d6a29f |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc60e0d7208190966797ce5f95fe49 |
completed | April 1, 2026, 12:03 a.m. |
Created at: March 30, 2026, 6:59 p.m.