Triple
T6358168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helen Hayes Theatre |
E143042
|
entity |
| Predicate | hasSoundSystem |
P70173
|
FINISHED |
| Object | theatrical sound reinforcement |
—
|
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: theatrical sound reinforcement | Statement: [Helen Hayes Theatre, hasSoundSystem, theatrical sound reinforcement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoundSystem Context triple: [Helen Hayes Theatre, hasSoundSystem, theatrical sound reinforcement]
-
A.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
B.
hasPartialSound
Indicates that one entity’s sound is included as a component or segment within the sound of another entity.
-
C.
hasVoiceSystem
Indicates that one entity possesses or is equipped with a particular voice-based system or voice technology.
-
D.
hasSpaceThemedSound
Indicates that something features or uses audio whose style, effects, or ambience evoke a space or sci‑fi theme.
-
E.
hasSpeakerType
Indicates that an entity functions in a particular role or category as a speaker (e.g., narrator, character, announcer) within a given context.
- 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.