Triple
T3170301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Wonderful Guy |
E66313
|
entity |
| Predicate | hasBroadwayOpeningContext |
P46720
|
FINISHED |
| Object | South Pacific Broadway premiere in 1949 |
—
|
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: South Pacific Broadway premiere in 1949 | Statement: [A Wonderful Guy, hasBroadwayOpeningContext, South Pacific Broadway premiere in 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroadwayOpeningContext Context triple: [A Wonderful Guy, hasBroadwayOpeningContext, South Pacific Broadway premiere in 1949]
-
A.
hasBroadwayProduction
Indicates that a work or show has been produced and staged in a Broadway theater.
-
B.
offBroadwayOpeningDate
Indicates the date on which a production first opened in an Off-Broadway venue.
-
C.
originalBroadwayOpeningDate
Indicates the calendar date on which a production first opened on Broadway in its original run.
-
D.
broadwayRunStatus
Indicates the status of a production’s run on Broadway, such as whether it is upcoming, currently running, or has closed.
-
E.
hasBroadwayTitle
Indicates that an entity is associated with a specific title used for its Broadway production or representation.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69ada20880e481908ecac09d49b1f1c3 |
completed | March 8, 2026, 4:21 p.m. |
Created at: March 8, 2026, 3:06 p.m.