Triple
T6358172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helen Hayes Theatre |
E143042
|
entity |
| Predicate | audienceAccess |
P70174
|
FINISHED |
| Object | ticketed entry |
—
|
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: ticketed entry | Statement: [Helen Hayes Theatre, audienceAccess, ticketed entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceAccess Context triple: [Helen Hayes Theatre, audienceAccess, ticketed entry]
-
A.
audienceSetting
Indicates the context or environment in which an audience is situated or addressed.
-
B.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
-
C.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
D.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
E.
audienceScale
Indicates the relative size or reach of the audience associated with an entity, event, or communication.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067f5bdd481909cf9db595ddb27df |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ec091c8190912aac44e1b8b1c9 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:32 p.m.