Triple

T2788660
Position Surface form Disambiguated ID Type / Status
Subject Bladensburg, Maryland E61872 entity
Predicate hasHistoricMarker P43592 FINISHED
Object Battle of Bladensburg historic markers 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: Battle of Bladensburg historic markers | Statement: [Bladensburg, Maryland, hasHistoricMarker, Battle of Bladensburg historic markers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricMarker
Context triple: [Bladensburg, Maryland, hasHistoricMarker, Battle of Bladensburg historic markers]
  • A. hasHistoricalEntity
    Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
  • B. isHistoric
    Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
  • C. hasHistoricalSection
    Indicates that something includes a dedicated part or segment that presents historical information or context.
  • D. hasHistoricalEvent
    Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
  • E. hasHistorySince
    Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
  • 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_69ab4b7f51d881908768300ebd2fbdae completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdeea881481908d759c72798a50fb completed March 7, 2026, 8:16 a.m.
PD Predicate disambiguation batch_69abdd025c948190a97dd961a9592bac completed March 7, 2026, 8:08 a.m.
PDg Predicate description generation batch_69abdee94c2081908e5075e87e70780a completed March 7, 2026, 8:16 a.m.
Created at: March 6, 2026, 9:58 p.m.