Triple
T12545773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St George's Hall, Windsor Castle |
E299964
|
entity |
| Predicate | hasAcousticUse |
P105816
|
FINISHED |
| Object | speeches and toasts |
—
|
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: speeches and toasts | Statement: [St George's Hall, Windsor Castle, hasAcousticUse, speeches and toasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAcousticUse Context triple: [St George's Hall, Windsor Castle, hasAcousticUse, speeches and toasts]
-
A.
hasAcousticVersionBy
Indicates that one entity is an acoustic version of another, created or performed by a specified agent.
-
B.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
C.
hasAcousticDemoVersion
Indicates that an entity has a version or recording presented in an acoustic demo form.
-
D.
hasAudioFeature
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
E.
usesAudioFrom
Indicates that one entity incorporates or relies on the audio content produced or provided by another entity.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d95f5148948190946a575d812b329d |
completed | April 10, 2026, 8:36 p.m. |
Created at: April 8, 2026, 9:57 p.m.