Triple
T1171916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beanpot tournament |
E24930
|
entity |
| Predicate | audienceEmotion |
P15291
|
FINISHED |
| Object | highly emotional atmosphere |
—
|
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: highly emotional atmosphere | Statement: [Beanpot tournament, audienceEmotion, highly emotional atmosphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceEmotion Context triple: [Beanpot tournament, audienceEmotion, highly emotional atmosphere]
-
A.
viewOnEmotion
Indicates a relationship where one entity holds a particular emotional perspective, reaction, or attitude toward another entity or situation.
-
B.
hasAudienceReception
chosen
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
-
C.
approximateAudienceSize
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
D.
faceExpression
Indicates the specific facial expression an entity is displaying, capturing its visible emotional or expressive state.
-
E.
audienceSizeApproximate
Indicates an estimated or approximate number of people in the audience for an event or content.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bceb3f188190b8b767380fe5986f |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5656948190b0b1d5446ad06005 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.