Triple

T22815405
Position Surface form Disambiguated ID Type / Status
Subject Redones E565082 entity
Predicate territoryCharacter P30854 FINISHED
Object western Armorican interior 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: western Armorican interior | Statement: [Redones, territoryCharacter, western Armorican interior]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: territoryCharacter
Context triple: [Redones, territoryCharacter, western Armorican interior]
  • A. regionCharacter chosen
    Indicates a characteristic, feature, or quality that typifies or defines a particular region.
  • B. governedTerritoryCharacteristic
    Indicates that a governing entity is associated with a specific characteristic or attribute of the territory it governs.
  • C. territoryType
    Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
  • D. territoryCorrespondedTo
    Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
  • E. territoryRepresentation
    Indicates that one entity serves as a representation, model, or depiction of a specific territory or geographic area for another 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_69e2458426188190b58b8ab4844fe420 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17dcb872881909a031d8560635fce completed April 29, 2026, 3:40 a.m.
PD Predicate disambiguation batch_69eed2cb30f481909566369f515f6eff completed April 27, 2026, 3:06 a.m.
Created at: April 17, 2026, 3:33 p.m.