Triple

T1248638
Position Surface form Disambiguated ID Type / Status
Subject Honeywell E26823 entity
Predicate notableClientSector P20603 FINISHED
Object commercial aviation 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: commercial aviation | Statement: [Honeywell, notableClientSector, commercial aviation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableClientSector
Context triple: [Honeywell, notableClientSector, commercial aviation]
  • A. notableIndustry
    Indicates that an entity is significantly recognized or prominent within a specified industry or sector.
  • B. notableEmployer
    Indicates that an entity has been employed by, or has worked for, a particularly significant or noteworthy organization or individual.
  • C. sectorInfluence
    Indicates the degree to which one sector affects, shapes, or exerts control over another sector or over outcomes within that sector.
  • D. hasIndustrialSector chosen
    Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
  • E. economicSectorSourceOfWealth
    Indicates that a particular economic sector is the primary source from which an entity derives its wealth or income.
  • 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_69a49487a9c48190ba9b05348fd1b53f completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4bf827e088190a16d845cea14f2c9 completed March 1, 2026, 10:36 p.m.
PD Predicate disambiguation batch_69a4bb6b075881908e867c25b5080e25 completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:47 p.m.