Triple

T8198599
Position Surface form Disambiguated ID Type / Status
Subject Borough of Fairfield E191501 entity
Predicate hasHistoricContext P1409 FINISHED
Object American Civil War region 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: American Civil War region | Statement: [Borough of Fairfield, hasHistoricContext, American Civil War region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricContext
Context triple: [Borough of Fairfield, hasHistoricContext, American Civil War region]
  • A. hasHistoricalContext chosen
    Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
  • B. hasHistoricalSection
    Indicates that something includes a dedicated part or segment that presents historical information or context.
  • C. hasHistoricalOrigin
    Indicates that something originated, was first established, or came into existence during a specific historical period or context.
  • D. isHistoric
    Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
  • E. hasHistoricalText
    Indicates that an entity is associated with a historical written document or record describing it or its 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_69ca82c6e9548190a4c5ca14516e4417 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb5df426cc81908b676d3d6852e29f completed March 31, 2026, 5:39 a.m.
PD Predicate disambiguation batch_69cb36aac86081909b83636e352e0ced completed March 31, 2026, 2:51 a.m.
Created at: March 30, 2026, 5:42 p.m.