Triple

T21335401
Position Surface form Disambiguated ID Type / Status
Subject Brabantse mainland E526031 entity
Predicate contains P35 FINISHED
Object Eindhoven 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: Eindhoven | Statement: [Brabantse mainland, contains, Eindhoven]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eindhoven
Context triple: [Brabantse mainland, contains, Eindhoven]
  • A. Eindhoven chosen
    Eindhoven is a major city in the southern Netherlands known for its industrial and technological significance, particularly as a hub for electronics and design.
  • B. Tilburg
    Tilburg is a city in the southern Netherlands known historically as an industrial and textile center and now as a regional cultural and educational hub.
  • C. Nijmegen
    Nijmegen is a historic Dutch city near the German border that played a crucial strategic role during World War II, particularly in the Allied advance in 1944.
  • D. Heerlen
    Heerlen is a city in the southeastern Netherlands known for its mining history and modernist architecture, located in the province of Limburg.
  • E. Utrecht
    Utrecht is a historic city and province in the central Netherlands, known for its medieval old town, canals, and role as a religious and cultural center.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b51c33048190ab27cede74ef798c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e898d6fcbc8190b83d9cfc9b4ca123 completed April 22, 2026, 9:45 a.m.
Created at: April 16, 2026, 4:43 p.m.