Triple

T30593824
Position Surface form Disambiguated ID Type / Status
Subject James York E778732 entity
Predicate roleInLocalHistoryStatus P29914 FINISHED
Object uncertain 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: uncertain | Statement: [James York, roleInLocalHistoryStatus, uncertain]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInLocalHistoryStatus
Context triple: [James York, roleInLocalHistoryStatus, uncertain]
  • A. historicalStatusOf
    Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
  • B. hasLocalHistoricalAssociations
    Indicates that something is connected to historically significant events, people, or developments specific to a particular locality or region.
  • C. roleInHistoryOf
    Indicates that one entity holds a specific role, contribution, or significance within the historical development or narrative of another entity.
  • D. hasLocalGovernmentHistory
    Indicates that an entity has a documented history or record of its local governmental structure, activities, or developments.
  • E. hasHistoricalRoleAs chosen
    Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
  • 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_69f224a1570c8190a85d3ac330479a79 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69ff7595c9bc8190982c6e6e07a0c78f completed May 9, 2026, 5:57 p.m.
PD Predicate disambiguation batch_69ff715432a88190a25670d26614bde2 completed May 9, 2026, 5:39 p.m.
Created at: April 29, 2026, 8:24 p.m.