Triple
T2326633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodgers and Hammerstein musicals |
E48301
|
entity |
| Predicate | hasWorkWithForm |
P26269
|
FINISHED |
| Object | two-act musical |
—
|
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: two-act musical | Statement: [Rodgers and Hammerstein musicals, hasWorkWithForm, two-act musical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkWithForm Context triple: [Rodgers and Hammerstein musicals, hasWorkWithForm, two-act musical]
-
A.
hasForm
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
B.
formsWith
Indicates that one entity combines or associates with another to create or constitute a joint structure, group, or configuration.
-
C.
containsForm
Indicates that one entity includes or encapsulates another entity as a form, structure, or representation within it.
-
D.
usesForm
chosen
Indicates that one entity employs, applies, or operates through a particular form, format, or structured representation of something.
-
E.
formOfWork
Indicates that one creative work is a specific form, version, or expression of another related work.
- 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_69a88aa308a88190b0b86c011fda7fce |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abcc30c5e881908c5d526d7e7491d0 |
completed | March 7, 2026, 6:56 a.m. |
| PD | Predicate disambiguation | batch_69abc5926d048190a535e3f23d41de2a |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:50 p.m.