Triple
T6455610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uproar |
E141985
|
entity |
| Predicate | featuresDanceChallenge |
P36067
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Uproar, featuresDanceChallenge, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresDanceChallenge Context triple: [Uproar, featuresDanceChallenge, Yes]
-
A.
featuresDanceNumber
Indicates that the subject includes or presents a dance performance or choreographed dance sequence.
-
B.
featuresDanceTeam
Indicates that something includes or presents a dance team as part of its composition, offering, or program.
-
C.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
-
D.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
E.
associatedDanceTrend
chosen
Indicates a relationship where one entity is linked to, or commonly recognized as having, a particular dance trend connected with it.
- 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_69c008d2f91c8190a8178767a35e08fc |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069d4d588819090e8a56c46c0bfe9 |
completed | March 22, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:48 p.m.