Triple
T4264829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disco Demolition Night |
E96797
|
entity |
| Predicate | impactOnBaseball |
P52396
|
FINISHED |
| Object | cautionary example for future promotions |
—
|
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: cautionary example for future promotions | Statement: [Disco Demolition Night, impactOnBaseball, cautionary example for future promotions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnBaseball Context triple: [Disco Demolition Night, impactOnBaseball, cautionary example for future promotions]
-
A.
impactOnField
chosen
Indicates the effect or influence that one entity, action, or development has on a particular field or domain.
-
B.
seasonImpact
Indicates how a particular season influences or affects another entity, condition, or outcome.
-
C.
ballpark
Indicates an approximate or rough estimation of a value, rather than an exact or precise figure.
-
D.
closedToBaseball
Indicates that something is not open, available, or accessible for playing or watching baseball.
-
E.
homeBaseballField
Indicates that one entity serves as the primary or designated baseball field used as the home venue by the other entity.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fcad0a881908e1cac0a6da5a321 |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.