Triple
T1460088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bench |
E31490
|
entity |
| Predicate | cheeringStyle |
P13362
|
FINISHED |
| Object | standing and yelling throughout the game |
—
|
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: standing and yelling throughout the game | Statement: [The Bench, cheeringStyle, standing and yelling throughout the game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cheeringStyle Context triple: [The Bench, cheeringStyle, standing and yelling throughout the game]
-
A.
hasCheerleaders
Indicates that an entity is associated with or supported by one or more cheerleaders.
-
B.
fanChant
Indicates a relationship where a group of fans collectively chant or vocalize in support of, or in response to, a person, team, or performance.
-
C.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
D.
performanceStyle
chosen
Indicates the manner or style in which an action, work, or performance is carried out or presented.
-
E.
officialCheerleadersFor
Indicates that one entity serves as the formally recognized cheerleading squad or group supporting another entity, such as a team or organization.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59d6dd88190b8ff3bda90aef7e2 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.