Triple
T5874171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA Three-Point Contest |
E130586
|
entity |
| Predicate | eventTime |
P19113
|
FINISHED |
| Object | during NBA All-Star Saturday Night |
—
|
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: during NBA All-Star Saturday Night | Statement: [NBA Three-Point Contest, eventTime, during NBA All-Star Saturday Night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventTime Context triple: [NBA Three-Point Contest, eventTime, during NBA All-Star Saturday Night]
-
A.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
-
B.
timePeriodEvent
Indicates that an event occurs, is scheduled, or is valid within a specified time period.
-
C.
presentedAtTime
Indicates that an event, action, or item was presented or occurred at a specific point in time.
-
D.
eventIn
chosen
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
E.
eventUsage
Indicates how an event is employed, applied, or utilized within a particular context or process.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.