Triple
T9466493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cameron Crazies |
E228283
|
entity |
| Predicate | cheerStyle |
P71645
|
FINISHED |
| Object | organized, coordinated chants |
—
|
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: organized, coordinated chants | Statement: [Cameron Crazies, cheerStyle, organized, coordinated chants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cheerStyle Context triple: [Cameron Crazies, cheerStyle, organized, coordinated chants]
-
A.
hasCheerStyle
chosen
Indicates that an entity possesses or is associated with a particular style or manner of cheering.
-
B.
hasCheerleaders
Indicates that an entity is associated with or supported by one or more cheerleaders.
-
C.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
D.
officialCheerleadersFor
Indicates that one entity serves as the formally recognized cheerleading squad or group supporting another entity, such as a team or organization.
-
E.
kickingStyle
Indicates the manner or technique with which an entity performs a kicking action in a given context.
- 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fdc08f08190ad17de08d2c2eca2 |
completed | April 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:53 p.m.