Triple
T1357713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1994–95 MLB strike |
E29025
|
entity |
| Predicate | fanImpact |
P22810
|
FINISHED |
| Object | decline in MLB attendance after strike |
—
|
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: decline in MLB attendance after strike | Statement: [1994–95 MLB strike, fanImpact, decline in MLB attendance after strike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanImpact Context triple: [1994–95 MLB strike, fanImpact, decline in MLB attendance after strike]
-
A.
sportsInfluence
chosen
Indicates a relationship where one entity affects, shapes, or contributes to another entity’s involvement, performance, or outcomes in sports.
-
B.
fanbaseCharacteristic
Indicates a characteristic, trait, or common quality that typically describes or distinguishes the fanbase of an entity.
-
C.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
D.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
E.
fanBelief
Indicates that a fan holds a particular belief, opinion, or conviction about someone or something.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c28f5b988190b0be4504eabb919d |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.