Triple

T6838513
Position Surface form Disambiguated ID Type / Status
Subject Essequibo E157510 entity
Predicate mergedWith P77 FINISHED
Object Berbice E162239 NE 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: Berbice | Statement: [Essequibo, mergedWith, Berbice]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Berbice
Context triple: [Essequibo, mergedWith, Berbice]
  • A. Berbice chosen
    Berbice was a former Dutch and later British colony on the northern coast of South America, in what is now part of Guyana.
  • B. Essequibo
    Essequibo was a former Dutch colony in the Guianas, centered on the Essequibo River region, that later became part of British Guiana.
  • C. Manicoré
    Manicoré is a municipality in the Brazilian state of Amazonas, located in the Amazon rainforest and known for its riverside economy and access to regional river transport routes.
  • D. Berbice River
    The Berbice River is a major river in eastern Guyana that flows northward into the Atlantic Ocean, historically important for inland transport and colonial-era settlements.
  • E. Lobito
    Lobito is a coastal city and major port in western Angola, known for its strategic harbor and role in the country’s trade and transport.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c6882c53608190b99aebef079b23bd completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d67ee1c88190b82a9b6b3d1e3875 completed March 27, 2026, 7:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69c72fb02e0c8190ae1514875e03208a completed March 28, 2026, 1:32 a.m.
Created at: March 27, 2026, 2:19 p.m.