Triple

T26243308
Position Surface form Disambiguated ID Type / Status
Subject Cambridge Sound Management E656371 entity
Predicate solutionCategory P4453 FINISHED
Object building acoustics 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: building acoustics | Statement: [Cambridge Sound Management, solutionCategory, building acoustics]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: solutionCategory
Context triple: [Cambridge Sound Management, solutionCategory, building acoustics]
  • A. solutionType chosen
    Indicates the specific category or kind of solution associated with an entity or problem.
  • B. solution
    Indicates that one entity is a mixture or substance formed by dissolving another entity (the solute) in a solvent, or more generally a means of solving or resolving a problem involving another entity.
  • C. providesSolutionFor
    Indicates that one entity offers or supplies a remedy, answer, or resolution to a problem, need, or issue associated with another entity.
  • D. solutionProperty
    Indicates that a solution possesses a specific characteristic, attribute, or quality relevant to its behavior, composition, or performance.
  • E. solutionDomain
    Indicates the conceptual or practical area in which a particular problem is addressed or solved.
  • 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_69ee5b4c59a881909d9ee4fd013fffd5 completed April 26, 2026, 6:37 p.m.
NER Named-entity recognition batch_69f60d90a5908190a7ccff2bd50ffe73 completed May 2, 2026, 2:43 p.m.
PD Predicate disambiguation batch_69f5f7fd90fc81909055b211368f9139 completed May 2, 2026, 1:11 p.m.
Created at: April 26, 2026, 9:04 p.m.