Triple

T3471180
Position Surface form Disambiguated ID Type / Status
Subject Durham, England E73260 entity
Predicate hasHistoricCoreOn P16505 FINISHED
Object peninsula in a meander of the River Wear 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: peninsula in a meander of the River Wear | Statement: [Durham, England, hasHistoricCoreOn, peninsula in a meander of the River Wear]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricCoreOn
Context triple: [Durham, England, hasHistoricCoreOn, peninsula in a meander of the River Wear]
  • 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. historicalCoreOf chosen
    Indicates that one entity constitutes the original or most historically significant central part of another entity.
  • C. isHistoric
    Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
  • D. hasHistoricalSection
    Indicates that something includes a dedicated part or segment that presents historical information or context.
  • 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.

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_69ad85b2fed48190948c8765e453d270 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adbb3af0cc81909e575828caeaeae0 completed March 8, 2026, 6:08 p.m.
PD Predicate disambiguation batch_69adae07802c8190919c49b0e65b2797 completed March 8, 2026, 5:12 p.m.
Created at: March 8, 2026, 3:17 p.m.