Triple

T2194700
Position Surface form Disambiguated ID Type / Status
Subject Court of Proprietors E49943 entity
Predicate couldDismiss P30055 FINISHED
Object directors of the British East India Company 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: directors of the British East India Company | Statement: [Court of Proprietors, couldDismiss, directors of the British East India Company]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: couldDismiss
Context triple: [Court of Proprietors, couldDismiss, directors of the British East India Company]
  • A. canResign
    Indicates that an entity has the authority or option to voluntarily leave a position, role, or membership.
  • B. couldPass
    Indicates that one entity had the ability or potential to move through, overcome, or be accepted by another entity or barrier.
  • C. canDismissCabinet chosen
    Indicates that one entity has the authority or power to remove or dismiss a cabinet from its official position.
  • D. canBeAppealedTo
    Indicates that a decision, action, or authority is subject to being challenged or reviewed by a higher or alternative authority through an appeal process.
  • E. couldIssue
    Indicates that one entity has the authority or ability to issue something (such as a document, command, or resource) to another entity.
  • 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_69a88aaba3c48190b351cab9b26989ff completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abbf764e348190896af2aeb5520038 completed March 7, 2026, 6:02 a.m.
PD Predicate disambiguation batch_69abbda52328819089c7ab111bebb0ca completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:46 p.m.