Triple
T3169609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Getting to Know You |
E66294
|
entity |
| Predicate | musicalTheatreGenre |
P41553
|
FINISHED |
| Object | Broadway show tune |
—
|
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: Broadway show tune | Statement: [Getting to Know You, musicalTheatreGenre, Broadway show tune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicalTheatreGenre Context triple: [Getting to Know You, musicalTheatreGenre, Broadway show tune]
-
A.
theatricalGenre
chosen
Indicates the specific theatrical genre or style to which a performance, play, or production belongs.
-
B.
hasMusicalTheatreOrigin
Indicates that something originates from, was first created for, or is primarily derived from musical theatre.
-
C.
theatreType
Indicates the specific category or kind of theatre associated with an entity, such as its format, style, or operational model.
-
D.
genreSpecialty
Indicates that an entity specializes in or is particularly associated with a specific genre.
-
E.
musicalRole
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada64917e08190bf0466d2c5e43790 |
completed | March 8, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0076b4819094628f1ad10b8f68 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.