Triple

T3384392
Position Surface form Disambiguated ID Type / Status
Subject Eindhoven Strijp-S E71260 entity
Predicate connectsTo P845 FINISHED
Object Tilburg E134398 NE 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: Tilburg | Statement: [Eindhoven Strijp-S, connectsTo, Tilburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tilburg
Context triple: [Eindhoven Strijp-S, connectsTo, Tilburg]
  • A. Tilburg chosen
    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.
  • B. Eindhoven
    Eindhoven is a major city in the southern Netherlands known for its industrial and technological significance, particularly as a hub for electronics and design.
  • C. 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.
  • D. 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.
  • E. Hilversum
    Hilversum is a Dutch city known as the country’s main media and broadcasting center, located in the province of North Holland.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ad85a8fd9c819095ecedf838d2bf1b completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb5ec85d08190b28110157c39435f completed March 8, 2026, 5:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69ca5e06c8dc8190b7b25725fb0a96e8 completed March 30, 2026, 11:27 a.m.
Created at: March 8, 2026, 3:14 p.m.