Triple

T18704647
Position Surface form Disambiguated ID Type / Status
Subject Distinguished Engineer at Google E457339 entity
Predicate instanceOf P0 FINISHED
Object senior engineering position C40670 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: senior engineering position
Context triple: [Distinguished Engineer at Google, instanceOf, senior engineering position]
  • A. senior oversight role
    A senior oversight role is a high-level position responsible for monitoring, guiding, and ensuring the integrity, compliance, and strategic alignment of an organization’s activities and decisions.
  • B. executive position
    An executive position is a high-level organizational role responsible for setting strategic direction, making major decisions, and overseeing the performance and operations of a company or its key divisions.
  • C. senior clerical role
    A senior clerical role is a higher-level administrative position responsible for overseeing complex office tasks, ensuring accurate records and documentation, and often supervising junior clerical staff.
  • D. senior naval command position
    A senior naval command position is a high-ranking leadership role responsible for directing major naval units or formations, making strategic and operational decisions, and ensuring the effective readiness and employment of maritime forces.
  • E. senior clerical rank
    A senior clerical rank is a high-level position within a religious or administrative hierarchy, typically involving significant authority, oversight responsibilities, and decision-making power over lower-ranking clerical roles.
  • F. None of above. chosen

Provenance (1 batch)

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_69d8d392aad081909fe31aa03e6e97d1 completed April 10, 2026, 10:40 a.m.
Created at: April 10, 2026, 11:49 a.m.