Triple

T2203419
Position Surface form Disambiguated ID Type / Status
Subject Charter Act 1813 E50542 entity
Predicate exceptionToMonopolyEnd P36964 FINISHED
Object tea trade 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: tea trade | Statement: [Charter Act 1813, exceptionToMonopolyEnd, tea trade]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: exceptionToMonopolyEnd
Context triple: [Charter Act 1813, exceptionToMonopolyEnd, tea trade]
  • A. monopolyEndedBy
    Indicates that a previously existing monopoly was terminated or disrupted by a particular agent, event, or intervention.
  • B. monopolyRestricted
    Indicates that an entity’s monopoly power or exclusive control over a market, resource, or service is limited, regulated, or otherwise constrained.
  • C. monopolyOn
    Indicates that one entity has exclusive control or rights over a resource, market, or activity, preventing others from participating on equal terms.
  • D. monopolyConfirmedBy
    Indicates that the existence or status of a monopoly is validated or officially recognized by a specified confirming party or source.
  • E. lostMonopolyOnPower
    Indicates that an entity previously held exclusive control or authority but no longer maintains that sole dominance.
  • 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_69a88b044ab48190add007487680f009 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abbfa481308190bda187c03162e0b6 completed March 7, 2026, 6:03 a.m.
PD Predicate disambiguation batch_69abbda706f4819094de73e1d1d1f539 completed March 7, 2026, 5:54 a.m.
PDg Predicate description generation batch_69abbf35c994819088a093c412931de4 completed March 7, 2026, 6:01 a.m.
Created at: March 4, 2026, 7:46 p.m.