Triple

T20382863
Position Surface form Disambiguated ID Type / Status
Subject Coleraine, Minnesota E497882 entity
Predicate primaryHistoricalEmployer P129978 FINISHED
Object iron mining companies 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: iron mining companies | Statement: [Coleraine, Minnesota, primaryHistoricalEmployer, iron mining companies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryHistoricalEmployer
Context triple: [Coleraine, Minnesota, primaryHistoricalEmployer, iron mining companies]
  • A. formerEmployer
    Indicates that one entity previously employed the other but no longer does so.
  • B. parentEmployer
    Indicates that one organization is the direct or higher-level employer of another organization or entity.
  • C. previousCorporateAffiliation
    Indicates that an entity was formerly employed by, associated with, or part of a specified corporate organization before its current status or affiliation.
  • D. employerOrPrimaryClient chosen
    Indicates that one entity serves as the main employer or principal client of another entity in a work or service relationship.
  • E. employerIn
    Indicates that one entity serves as the employer of another within a specified context, such as a location, organization, or time 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_69e0b4a5b7908190a972e4e7e698ae94 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e678b208ec8190a09bf5fd947a2a02 completed April 20, 2026, 7:04 p.m.
PD Predicate disambiguation batch_69e57648be3c81908256838228cabf5c completed April 20, 2026, 12:41 a.m.
Created at: April 16, 2026, 11:27 a.m.