Triple
T2667605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Philadelphia Story |
E55673
|
entity |
| Predicate | theatricalGenre |
P41553
|
FINISHED |
| Object | Broadway play |
—
|
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 play | Statement: [The Philadelphia Story, theatricalGenre, Broadway play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theatricalGenre Context triple: [The Philadelphia Story, theatricalGenre, Broadway play]
-
A.
theatreType
Indicates the specific category or kind of theatre associated with an entity, such as its format, style, or operational model.
-
B.
theaterType
Indicates the specific kind or category of theater associated with an entity (e.g., cinema, opera house, drama theater).
-
C.
theater
Indicates that an entity is a theater or is functioning in the role of a theater (a venue where performances or films are shown).
-
D.
theatricalFunction
Indicates the role or purpose something serves within a theatrical context, such as its function in staging, performance, or dramatic presentation.
-
E.
theatre
Indicates that an entity is a theater or is associated with theatrical performances or activities.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd98a4ee88190aa7ef914e316ba31 |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8f98c348190a68064c565589459 |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:54 p.m.