Triple

T5045808
Position Surface form Disambiguated ID Type / Status
Subject Oddjob E113658 entity
Predicate loyaltyLevel P56014 FINISHED
Object fanatically loyal to employer 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: fanatically loyal to employer | Statement: [Oddjob, loyaltyLevel, fanatically loyal to employer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: loyaltyLevel
Context triple: [Oddjob, loyaltyLevel, fanatically loyal to employer]
  • A. loyaltyProgramTierOf
    Indicates the specific loyalty or rewards program tier that an entity (such as a customer or account) belongs to.
  • B. petitionerLoyaltyStatus chosen
    Indicates the current or historical loyalty or allegiance status of the petitioner in relation to a relevant authority, group, or cause.
  • C. loyaltyProgramType
    Indicates the specific category or kind of loyalty program associated with an entity (such as points-based, tiered, or subscription-based).
  • D. loyaltyDomain
    Indicates a relationship where loyalty, allegiance, or steadfast support is directed toward or governed by a particular domain, context, or sphere of influence.
  • E. loyaltyProgramName
    Indicates that an entity is associated with or identified by the name of a specific loyalty or rewards program.
  • 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_69bd44391fc48190a311ce9c826c209b completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd73fe99688190961708f5d8eb6bff completed March 20, 2026, 4:21 p.m.
PD Predicate disambiguation batch_69bd71529d608190a53470ba6c14bb1d completed March 20, 2026, 4:09 p.m.
Created at: March 20, 2026, 1:37 p.m.