Triple
T17633681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campoamor Theatre |
E430038
|
entity |
| Predicate | hasAcousticsQuality |
P117332
|
FINISHED |
| Object | good for opera |
—
|
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: good for opera | Statement: [Campoamor Theatre, hasAcousticsQuality, good for opera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAcousticsQuality Context triple: [Campoamor Theatre, hasAcousticsQuality, good for opera]
-
A.
hasAcousticsSuitableFor
chosen
Indicates that something possesses acoustic properties that are appropriate or well-suited for a particular use, activity, or environment.
-
B.
isAcoustic
Indicates that something produces sound using natural resonance or mechanical vibration rather than electronic amplification or synthesis.
-
C.
hasAcousticUse
Indicates that something is used or functions in relation to sound or acoustics.
-
D.
supportsAudioQuality
Indicates that one entity provides or is compatible with a specified level or type of audio quality for another entity or context.
-
E.
hasAcousticVersionBy
Indicates that one entity is an acoustic version of another, created or performed by a specified agent.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46ddea4688190a76a4225f268c0ac |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.