Triple

T30558320
Position Surface form Disambiguated ID Type / Status
Subject de Montmorency E777762 entity
Predicate hasTitleAssociatedTerritory P71755 FINISHED
Object Montmorency, Val-d’Oise 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: Montmorency, Val-d’Oise | Statement: [de Montmorency, hasTitleAssociatedTerritory, Montmorency, Val-d’Oise]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTitleAssociatedTerritory
Context triple: [de Montmorency, hasTitleAssociatedTerritory, Montmorency, Val-d’Oise]
  • A. associatedTitleTerritory chosen
    Indicates a relationship where a specific title is linked or connected to a particular territory or domain.
  • B. hasTerritorialAssociation
    Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
  • C. territoryCorrespondedTo
    Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
  • D. definedTerritoryOf
    Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
  • E. affectsTerritoryOf
    Indicates that one entity causes changes to, or has an impact on, the territorial domain or jurisdiction of 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_69f2249ed41c8190b175170ecfd6e1c5 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fb2e940d5c8190bceae77daf4ef512 completed May 6, 2026, 12:05 p.m.
PD Predicate disambiguation batch_69f9fec70bd881909c658a3c5020318b completed May 5, 2026, 2:29 p.m.
Created at: April 29, 2026, 8:21 p.m.