Triple

T23799579
Position Surface form Disambiguated ID Type / Status
Subject French Netherlands E588631 entity
Predicate historicalSubregion P915 FINISHED
Object Walloon Flanders 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: Walloon Flanders | Statement: [French Netherlands, historicalSubregion, Walloon Flanders]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalSubregion
Context triple: [French Netherlands, historicalSubregion, Walloon Flanders]
  • A. historicalRegion chosen
    Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
  • B. historicalCoreRegion
    Indicates that a region served as the central or foundational area of a group, state, or civilization during a significant historical period.
  • C. historicalAdministrativeRegionName
    Indicates the name assigned to an administrative region as it existed during a specific historical period.
  • D. historicalFocusRegion
    Indicates that an entity’s primary historical attention, study, or activity is centered on a particular geographic region.
  • E. historicalStatusOfRegion
    Indicates the historical political or administrative status that a region held during a specific past period.
  • 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_69e25d15db58819092ac1e6791696fd9 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1c6dfaae081908be48fa89e625f71 completed April 29, 2026, 8:52 a.m.
PD Predicate disambiguation batch_69f155fe300481909bd617443228df65 completed April 29, 2026, 12:51 a.m.
Created at: April 17, 2026, 7:52 p.m.