Triple

T32335578
Position Surface form Disambiguated ID Type / Status
Subject EC2M E826161 entity
Predicate hasSectorCode P44726 FINISHED
Object M 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: M | Statement: [EC2M, hasSectorCode, M]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSectorCode
Context triple: [EC2M, hasSectorCode, M]
  • A. hasSectorType
    Indicates that an entity belongs to or is classified under a particular sector category or type.
  • B. sectorCode chosen
    Indicates the classification code that identifies the economic or organizational sector associated with an entity or activity.
  • C. hasSectorClassificationStandard
    Indicates that an entity is associated with a particular sector classification standard used to categorize its industry or economic activity.
  • D. isSectorSpecific
    Indicates that something is tailored or restricted to a particular industry or sector rather than being generally applicable.
  • E. hasMarketSector
    Indicates that an entity operates within, is associated with, or belongs to a particular market sector or industry segment.
  • 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_69f34913d9048190befaa634025232be completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69ff49f888348190b9c55afa73b99e6a completed May 9, 2026, 2:51 p.m.
PD Predicate disambiguation batch_69ff49614ef88190ac70b034c55ad738 completed May 9, 2026, 2:49 p.m.
Created at: May 1, 2026, 12:48 a.m.