Triple

T9372
Position Surface form Disambiguated ID Type / Status
Subject Bolt Beranek and Newman E188 entity
Predicate specializedIn P466 FINISHED
Object acoustic consulting 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: acoustic consulting | Statement: [Bolt Beranek and Newman, specializedIn, acoustic consulting]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: specializedIn
Context triple: [Bolt Beranek and Newman, specializedIn, acoustic consulting]
  • A. hasSpecialty chosen
    Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
  • B. fieldOfWork
    Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
  • C. worksWith
    Indicates that two entities collaborate or perform tasks together in a shared work-related context.
  • D. recognizedAs
    Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
  • E. subjectMatter
    Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
  • 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_69a23bb612708190b09f25385e4b63d1 completed Feb. 28, 2026, 12:49 a.m.
NER Named-entity recognition batch_69a240b249788190af8dbf7e80e9c91b completed Feb. 28, 2026, 1:11 a.m.
PD Predicate disambiguation batch_69a23fe52ec48190a4d24101c91434ed completed Feb. 28, 2026, 1:07 a.m.
Created at: Feb. 28, 2026, 12:54 a.m.