Triple

T29762267
Position Surface form Disambiguated ID Type / Status
Subject Bavaria E753804 entity
Predicate hasHistoricTiesWith P7843 FINISHED
Object Habsburg territories 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: Habsburg territories | Statement: [Bavaria, hasHistoricTiesWith, Habsburg territories]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricTiesWith
Context triple: [Bavaria, hasHistoricTiesWith, Habsburg territories]
  • A. hasHistoricalTieTo chosen
    Indicates a relationship where one entity is historically connected or linked to another through past events, associations, or influences.
  • B. hasSharedBorderHistoryWith
    Indicates that two entities have a history of sharing a common border or boundary at some point in time.
  • C. historicalRelationsWith
    Indicates a relationship where one entity has documented or recognized connections, interactions, or associations with another entity in the past.
  • D. hasNegativeHistoricalAssociation
    Indicates that one entity is historically linked to another in a way that is viewed as harmful, problematic, or disreputable.
  • E. hasHeritageConnectionWith
    Indicates a relationship where two entities are linked through shared, inherited, or culturally transmitted heritage or ancestry.
  • 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_69f0ef827ff88190ade56e0b0846b713 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69fd6dbd1b648190b1a0b391c03aebc5 completed May 8, 2026, 4:59 a.m.
PD Predicate disambiguation batch_69fd6a9020548190bbfa845360ac85fb completed May 8, 2026, 4:46 a.m.
Created at: April 28, 2026, 8:34 p.m.