Triple

T31450965
Position Surface form Disambiguated ID Type / Status
Subject Cutting for Stone E802318 entity
Predicate centralProfession P103653 FINISHED
Object surgeon 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: surgeon | Statement: [Cutting for Stone, centralProfession, surgeon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: centralProfession
Context triple: [Cutting for Stone, centralProfession, surgeon]
  • A. professionalCategory chosen
    Indicates the classification of an entity according to its professional field, role, or occupational domain.
  • B. professionDeterminedBy
    Indicates that an entity’s profession is defined or decided based on another factor, condition, or entity.
  • C. professionalBase
    Indicates that one entity serves as the primary professional location, organization, or base of operations for another entity.
  • D. professionTransmission
    Indicates that a profession, trade, or occupational role is passed from one entity (often a person or group) to another, such as across generations or through teaching and mentorship.
  • E. publicCareer
    Indicates that an entity has held or pursued a role or occupation in the public sphere, such as government, politics, or other publicly visible service.
  • 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_69f348c678ac81908a2e950867619061 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fccdd496048190bca801a8a9eecb62 completed May 7, 2026, 5:37 p.m.
PD Predicate disambiguation batch_69fcccee6240819084680887731ff64b completed May 7, 2026, 5:33 p.m.
Created at: April 30, 2026, 9:13 p.m.