Triple

T33037713
Position Surface form Disambiguated ID Type / Status
Subject Bavarian Nordgau E845363 entity
Predicate hasHistoricalSourceType P59487 FINISHED
Object medieval charters 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: medieval charters | Statement: [Bavarian Nordgau, hasHistoricalSourceType, medieval charters]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricalSourceType
Context triple: [Bavarian Nordgau, hasHistoricalSourceType, medieval charters]
  • 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. hasTypeHistory
    Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
  • C. hasHistoricalService
    Indicates that an entity has previously provided service or fulfilled a role during a past historical period or event.
  • D. hasHistoricalData chosen
    Indicates that an entity possesses recorded information or records about past events, states, or values relevant to it.
  • E. hasHistoricalOrigin
    Indicates that something originated, was first established, or came into existence during a specific historical period or context.
  • 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_69f34951348c8190b56746b0a7018182 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69feafa1ba0081909013800b85a9f613 completed May 9, 2026, 3:53 a.m.
PD Predicate disambiguation batch_69feae58d62c81909d031f3df8992883 completed May 9, 2026, 3:47 a.m.
Created at: May 1, 2026, 1:24 a.m.