Triple
T1327964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game 7 |
E28372
|
entity |
| Predicate | hasEmotionalImpactOn |
P13275
|
FINISHED |
| Object | fans |
—
|
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: fans | Statement: [Game 7, hasEmotionalImpactOn, fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmotionalImpactOn Context triple: [Game 7, hasEmotionalImpactOn, fans]
-
A.
emotionallyAttachedTo
Indicates that one entity has a strong emotional bond, affection, or dependence directed toward another entity.
-
B.
viewOnEmotion
chosen
Indicates a relationship where one entity holds a particular emotional perspective, reaction, or attitude toward another entity or situation.
-
C.
influencedPerceptionOf
Indicates that one entity has affected, shaped, or altered how another entity is perceived or understood.
-
D.
involvedPhysicalEffect
Indicates that one entity participates in causing, experiencing, or mediating a physical effect on another entity or the environment.
-
E.
hasTragicPast
Indicates that an entity has experienced a significantly sorrowful or traumatic history that influences its present state or characterization.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c1d8188190b15a641a08345adc |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.