Triple
T33941525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorial Day Miracle |
E870178
|
entity |
| Predicate | occurredInSeries |
P9323
|
FINISHED |
| Object | 1999 Western Conference Finals |
—
|
NE NERFINISHED |
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: 1999 Western Conference Finals | Statement: [Memorial Day Miracle, occurredInSeries, 1999 Western Conference Finals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occurredInSeries Context triple: [Memorial Day Miracle, occurredInSeries, 1999 Western Conference Finals]
-
A.
situatedInSeries
Indicates that one entity is located or positioned within a particular series, sequence, or ordered collection of related items.
-
B.
basedInSeries
Indicates that one entity is set, located, or primarily takes place within the narrative world or context of a particular series.
-
C.
usedInSeries
Indicates that something (such as an element, component, or concept) is employed or appears within a particular series.
-
D.
occurredIn
chosen
Indicates that an event or action took place within a specific location, context, or time frame.
-
E.
airedWithinSeries
Indicates that an episode or installment was broadcast as part of, and within the run of, a particular series.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.