Triple

T14669914
Position Surface form Disambiguated ID Type / Status
Subject Electorate of Trier E344481 entity
Predicate hadTerritoryOn P28640 FINISHED
Object left bank of the Rhine 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: left bank of the Rhine | Statement: [Electorate of Trier, hadTerritoryOn, left bank of the Rhine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadTerritoryOn
Context triple: [Electorate of Trier, hadTerritoryOn, left bank of the Rhine]
  • A. wasCoreTerritoryOf
    Indicates that a region historically formed the central or most important territorial area belonging to a particular political or cultural entity.
  • B. hasHistoricTerritory
    Indicates that an entity possesses or claims a territory that it historically occupied, controlled, or was associated with in the past.
  • C. heldTerritory chosen
    Indicates that one entity maintained control or possession over a specific territory or geographic area.
  • D. lastTerritoriesConqueredBy
    Indicates that the referenced territories are the most recent ones taken control of through conquest by a specified entity.
  • E. acquiredTerritoryBy
    Indicates a relationship where one entity gains control or ownership of a territory through a specific means, event, or process.
  • 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_69d822e283fc8190a0e4c235cf880052 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb54ef2908190b189ced65eec434a completed April 14, 2026, 9:44 p.m.
PD Predicate disambiguation batch_69de6576f0208190aa94d995e797ac38 completed April 14, 2026, 4:04 p.m.
Created at: April 10, 2026, 1:27 a.m.