Triple

T1499761
Position Surface form Disambiguated ID Type / Status
Subject Altera E29768 entity
Predicate customerSegment P481 FINISHED
Object communications infrastructure 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: communications infrastructure | Statement: [Altera, customerSegment, communications infrastructure]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: customerSegment
Context triple: [Altera, customerSegment, communications infrastructure]
  • A. brandSegment
    Indicates the specific market segment or customer group that a brand is targeted toward or associated with.
  • B. customerType
    Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
  • C. targetMarket chosen
    Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
  • D. customerFocus
    Indicates that one entity prioritizes understanding and meeting the needs, preferences, or satisfaction of another entity (typically a customer or client).
  • E. majorCustomer
    Indicates that one entity is a primary or high-value customer of another entity, typically contributing a significant portion of business or revenue.
  • 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_69a498dba1d8819093b46a3a8d2485f1 completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c6f0ce988190aafab4a6e0dfd710 completed March 1, 2026, 11:08 p.m.
PD Predicate disambiguation batch_69a4c48a8cf48190a6ebf8d44a608a06 completed March 1, 2026, 10:58 p.m.
Created at: March 1, 2026, 8:12 p.m.