Triple

T35327020
Position Surface form Disambiguated ID Type / Status
Subject Fall River textile mills E1020213 entity
Predicate competitorWith P1375 FINISHED
Object Lowell textile mills NE NERFINISHED

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: Lowell textile mills | Statement: [Fall River textile mills, competitorWith, Lowell textile mills]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: competitorWith
Context triple: [Fall River textile mills, competitorWith, Lowell textile mills]
  • A. competesWith chosen
    Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
  • B. partnerInCompetition
    Indicates that two or more entities are collaborating as partners or teammates within the same competitive event or context.
  • C. competitorOwner
    Indicates that one entity owns or controls a business or asset that competes in the same market or domain as another entity’s business or asset.
  • D. competitionFrom
    Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
  • E. hadCompetitor
    Indicates that one entity was in a competitive relationship with another entity, typically operating in the same domain or market.
  • 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_69f76deacf4481908e7735a5a7715b0a completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcd867f36081908c88c55a6a1404c1 completed May 7, 2026, 6:22 p.m.
PD Predicate disambiguation batch_69fcd1f47b188190b4cf4b4c748d9d03 completed May 7, 2026, 5:55 p.m.
Created at: May 3, 2026, 4:03 p.m.