Triple

T8253114
Position Surface form Disambiguated ID Type / Status
Subject Spies E193003 entity
Predicate mayDeriveFromOccupation P8625 FINISHED
Object spearman 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: spearman | Statement: [Spies, mayDeriveFromOccupation, spearman]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayDeriveFromOccupation
Context triple: [Spies, mayDeriveFromOccupation, spearman]
  • A. derivesFromOccupation chosen
    Indicates that one entity originates from, is obtained through, or is a result of another entity’s occupation or professional role.
  • B. isOccupationalFormOf
    Indicates that one occupation is a specific form, variant, or specialization of another, more general occupation.
  • C. mayWorkIn
    Indicates that an entity is allowed or has the possibility to work in a particular place, organization, or context.
  • D. requiredOccupationOf
    Indicates that one entity specifies the occupation or job role that is required or expected for another entity (such as a position, task, or qualification).
  • E. endedOccupationOf
    Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
  • 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_69ca82dfad9c8190b8cd18fb89f50f40 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb78cbc7cc81909931440e95d6e691 completed March 31, 2026, 7:33 a.m.
PD Predicate disambiguation batch_69cb36b6d5548190b665a6cce14c69f7 completed March 31, 2026, 2:51 a.m.
Created at: March 30, 2026, 5:48 p.m.