Triple

T553643
Position Surface form Disambiguated ID Type / Status
Subject Northwest Passage E11895 entity
Predicate historicallySoughtBy P16288 FINISHED
Object European explorers 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: European explorers | Statement: [Northwest Passage, historicallySoughtBy, European explorers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallySoughtBy
Context triple: [Northwest Passage, historicallySoughtBy, European explorers]
  • A. historicallyIn
    Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
  • B. historicallyBorneBy
    Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
  • C. historicallyConsidered
    Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
  • D. historicallyPrizedFor
    Indicates that something has been especially valued or esteemed for a particular quality, use, or significance in the past.
  • E. historicalReference
    Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
  • 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_69a4932941d08190815efd422f0b4ca7 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4991b296481908cf27e1d1ec67052 completed March 1, 2026, 7:52 p.m.
PD Predicate disambiguation batch_69a494bc1f8c8190904356f3a8e801de completed March 1, 2026, 7:34 p.m.
PDg Predicate description generation batch_69a4985952a481908b918350ececf484 completed March 1, 2026, 7:49 p.m.
Created at: March 1, 2026, 7:32 p.m.