Triple
T14309918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee Room 4 |
E354798
|
entity |
| Predicate | audioVisualSupport |
P48651
|
FINISHED |
| Object | committee broadcasting systems |
—
|
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: committee broadcasting systems | Statement: [Committee Room 4, audioVisualSupport, committee broadcasting systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioVisualSupport Context triple: [Committee Room 4, audioVisualSupport, committee broadcasting systems]
-
A.
isAudioWorkForVisualWork
Indicates that one work serves as the audio component or soundtrack specifically created for or associated with a particular visual work.
-
B.
usesAudioFrom
Indicates that one entity incorporates or relies on the audio content produced or provided by another entity.
-
C.
depictsSound
Indicates that one entity visually represents or portrays the sound produced by another entity.
-
D.
hasAudioFeature
chosen
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
E.
visualCompanion
Indicates that one entity serves as a visual counterpart, partner, or accompanying element to another in a visual context.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b26da48190a96e2f60ace51335 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.