Triple

T33559305
Position Surface form Disambiguated ID Type / Status
Subject Sir John Woodward Green E859567 entity
Predicate likelyNotableFor P177624 FINISHED
Object distinguished service 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: distinguished service | Statement: [Sir John Woodward Green, likelyNotableFor, distinguished service]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: likelyNotableFor
Context triple: [Sir John Woodward Green, likelyNotableFor, distinguished service]
  • A. likelyNotability
    Indicates that an entity is assessed as probably not meeting a specified threshold of importance, prominence, or significance within a given context.
  • B. lacksNotabilityAs
    Indicates that one entity is considered insufficiently notable or significant to be associated with or classified as the other entity.
  • C. possibleCauseOfNotability
    Indicates that one entity is a potential reason or contributing factor for why another entity is notable or recognized.
  • D. hasNotablePeople
    Indicates that certain people associated with an entity are distinguished or noteworthy in some recognized way.
  • E. notableFor
    Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
  • F. None of above. chosen

Provenance (4 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_69f3497b2b68819093207971b5e13dc8 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7009d39508190af7301f824615e88 completed May 3, 2026, 8 a.m.
PD Predicate disambiguation batch_69f6fc5740fc81909774a4f65201a3ff completed May 3, 2026, 7:42 a.m.
PDg Predicate description generation batch_69f6ffb7554881908993d6d2ffbcf8f5 completed May 3, 2026, 7:56 a.m.
Created at: May 1, 2026, 1:40 a.m.