Triple

T26689299
Position Surface form Disambiguated ID Type / Status
Subject Lords of Joinville E672830 entity
Predicate typeOfTerritoryRuled P63456 FINISHED
Object seigneurie 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: seigneurie | Statement: [Lords of Joinville, typeOfTerritoryRuled, seigneurie]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfTerritoryRuled
Context triple: [Lords of Joinville, typeOfTerritoryRuled, seigneurie]
  • A. historicalTerritoryType chosen
    Indicates that a territory is classified according to a specific type or category it held during a historical period.
  • B. territoryLaterControlledBy
    Indicates that a territory was subsequently governed, ruled, or administered by a specified controlling entity after an earlier period.
  • C. wasCoreTerritoryOf
    Indicates that a region historically formed the central or most important territorial area belonging to a particular political or cultural entity.
  • D. countryRuled
    Indicates that one entity exercises governing authority or political control over a country.
  • E. governedTerritoryVia
    Indicates a relationship where an authority or governing body exercises control over a territory through an intermediary entity, mechanism, or arrangement.
  • 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_69eecda2066c8190a344218afa5e89c1 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69fd2a215d6c8190a1a428ccaee603f1 completed May 8, 2026, 12:11 a.m.
PD Predicate disambiguation batch_69fd28ef19688190bb8370f2812a43e7 completed May 8, 2026, 12:06 a.m.
Created at: April 27, 2026, 3:25 a.m.