Triple

T34992435
Position Surface form Disambiguated ID Type / Status
Subject Swithhelm of Essex E1009428 entity
Predicate rulingTerritory P10006 FINISHED
Object Essex 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: Essex | Statement: [Swithhelm of Essex, rulingTerritory, Essex]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rulingTerritory
Context triple: [Swithhelm of Essex, rulingTerritory, Essex]
  • A. governedTerritory chosen
    Indicates that one entity exercises political authority or control over another entity or geographic area as its governing power.
  • B. governedTerritoryVia
    Indicates a relationship where an authority or governing body exercises control over a territory through an intermediary entity, mechanism, or arrangement.
  • C. governedTerritoryWith
    Indicates that one entity exercised governing authority or control over a specified territory, region, or domain in association with another entity.
  • D. seatOfSovereignty
    Indicates that a location serves as the primary center of governing authority or ruling power for a political entity.
  • E. wasCoreTerritoryOf
    Indicates that a region historically formed the central or most important territorial area belonging to a particular political or cultural entity.
  • 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_69f76dca50dc8190b71f39defe186be8 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78710282c81909146dc0be91e983f completed May 3, 2026, 5:34 p.m.
PD Predicate disambiguation batch_69f784162134819098413482ef52042f completed May 3, 2026, 5:21 p.m.
Created at: May 3, 2026, 4:01 p.m.