Triple

T2712428
Position Surface form Disambiguated ID Type / Status
Subject Bight of Benin E59892 entity
Predicate historicalNameUsage P2834 FINISHED
Object used in European maritime charts 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: used in European maritime charts | Statement: [Bight of Benin, historicalNameUsage, used in European maritime charts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalNameUsage
Context triple: [Bight of Benin, historicalNameUsage, used in European maritime charts]
  • A. regionHistoricalName
    Indicates that a region has been known by a particular historical name during some past period.
  • B. historicallyRecognizedAs
    Indicates that an entity has been acknowledged or designated under a particular name, status, or role during a past historical period.
  • C. historicallyBorneBy chosen
    Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
  • D. historicalEraOfNaming
    Indicates the historical era or time period during which an entity received its name.
  • E. historicallyAdoptedBy
    Indicates that something (such as a practice, policy, idea, or object) was used or taken up by an entity at some point in the past.
  • 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_69ab4ac92a088190bc74bca14038e3de completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abda90d5a88190bcb6caefd8f2dd1b completed March 7, 2026, 7:58 a.m.
PD Predicate disambiguation batch_69abd8224c688190bb4a362360b03007 completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:55 p.m.