Triple

T4928883
Position Surface form Disambiguated ID Type / Status
Subject Chief Hancock E110642 entity
Predicate hasSignificantRoleIn P27764 FINISHED
Object history of Native-colonial relations in the Carolinas 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: history of Native-colonial relations in the Carolinas | Statement: [Chief Hancock, hasSignificantRoleIn, history of Native-colonial relations in the Carolinas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSignificantRoleIn
Context triple: [Chief Hancock, hasSignificantRoleIn, history of Native-colonial relations in the Carolinas]
  • A. hasNotableRoleIn chosen
    Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
  • B. hasCapitalRole
    Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
  • C. hasMainRole
    Indicates that an entity holds the primary or most significant role in relation to another entity or context.
  • D. playedKeyRoleIn
    Indicates that an entity had a major, influential, or decisive impact on the occurrence, outcome, or success of another entity or event.
  • E. significantEventRole
    Indicates that an entity plays an important or defining role in a particular significant event.
  • 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_69bd4415190c8190817bee7ec9f9f944 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd7038c12c81908a793b4a8768c28a completed March 20, 2026, 4:05 p.m.
PD Predicate disambiguation batch_69bd6c3695c8819094e7ad2f6d4ba1ac completed March 20, 2026, 3:48 p.m.
Created at: March 20, 2026, 1:30 p.m.