Triple

T11223164
Position Surface form Disambiguated ID Type / Status
Subject Bucoda, Washington E265622 entity
Predicate hasMajorHistoricalPeriod P4928 FINISHED
Object 19th-century coal mining era 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: 19th-century coal mining era | Statement: [Bucoda, Washington, hasMajorHistoricalPeriod, 19th-century coal mining era]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMajorHistoricalPeriod
Context triple: [Bucoda, Washington, hasMajorHistoricalPeriod, 19th-century coal mining era]
  • A. historicalPeriodOfMajorActivity
    Indicates the historical period during which an entity carried out its most significant or influential activities.
  • B. historicalPeriodOfSignificance chosen
    Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
  • C. hasHistoricalEvent
    Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
  • D. hasHistoricalSection
    Indicates that something includes a dedicated part or segment that presents historical information or context.
  • E. hasNearbyHistoricPeriod
    Indicates that one historic period occurs close in time or space to another historic period.
  • 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_69d6aac59460819089b9848b27f57848 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8ec8fb08190b27144ab65f85957 completed April 9, 2026, 5:59 p.m.
PD Predicate disambiguation batch_69d75cfbbb188190861efd5d94fe27da completed April 9, 2026, 8:02 a.m.
Created at: April 8, 2026, 9:30 p.m.