Triple
T22802838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadway Rhythm |
E564445
|
entity |
| Predicate | featuresEnsemblePerformances |
P88799
|
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: [Broadway Rhythm, featuresEnsemblePerformances, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresEnsemblePerformances Context triple: [Broadway Rhythm, featuresEnsemblePerformances, yes]
-
A.
featuresPerformanceBy
Indicates a relationship where something (such as an event, work, or production) includes or showcases a performance given by a particular performer or group.
-
B.
performsFeat
Indicates that an entity carries out or accomplishes a notable or significant feat.
-
C.
featuresScoreBy
Indicates a scoring relationship where a feature or set of features is evaluated and assigned a score according to a specified criterion or entity.
-
D.
featuresScoringSystem
Indicates that one entity incorporates or provides a particular scoring or rating system as part of its functionality or design.
-
E.
featuresVocalEnsemble
chosen
Indicates that something includes or presents a group of vocal performers singing together.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cdf1e308190a05d0f61856be544 |
completed | April 29, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:31 p.m.