Triple
T1167527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New England Patriots Cheerleaders |
E24831
|
entity |
| Predicate | hasTypeOfPerformance |
P20624
|
FINISHED |
| Object | choreographed dance routines |
—
|
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: choreographed dance routines | Statement: [New England Patriots Cheerleaders, hasTypeOfPerformance, choreographed dance routines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfPerformance Context triple: [New England Patriots Cheerleaders, hasTypeOfPerformance, choreographed dance routines]
-
A.
performerType
chosen
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
B.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasOrchestraType
Indicates that an entity is associated with, or classified by, a specific type or category of orchestra.
-
E.
performedInSceneType
Indicates that an action or event was carried out within a scene of a specified type or category.
- 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_69a4bccd75048190b8ce88237c1a748b |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb548c1481909092626c572d8782 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.