Triple

T3677661
Position Surface form Disambiguated ID Type / Status
Subject Vijfhuizen E78033 entity
Predicate hasDefensiveStructure P22477 FINISHED
Object Fort Vijfhuizen E381486 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: Fort Vijfhuizen | Statement: [Vijfhuizen, hasDefensiveStructure, Fort Vijfhuizen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fort Vijfhuizen
Context triple: [Vijfhuizen, hasDefensiveStructure, Fort Vijfhuizen]
  • A. Fort Vijfhuizen chosen
    Fort Vijfhuizen is a historic Dutch fort that forms part of the UNESCO-listed Defence Line of Amsterdam, now often used for cultural and recreational purposes.
  • B. Voorburg
    Voorburg is a historic town in the Netherlands, now part of the municipality of Leidschendam-Voorburg, known for its rich cultural heritage and proximity to The Hague.
  • C. Soestdijk
    Soestdijk is a village in the Netherlands known for its historic royal residence, Soestdijk Palace.
  • D. ’s-Heer Arendskerke
    ’s-Heer Arendskerke is a small village in the Dutch province of Zeeland, known for its rural character and historic church.
  • E. Diksmuide
    Diksmuide is a historic town in western Belgium known for its World War I battlefields and memorials, particularly the Yser Tower.
  • 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_69ad85e18c1c8190be8aafb227f39f48 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc4643cf08190b2d10ddf4aac7407 completed March 8, 2026, 6:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4daffd6bc81908ac7a4b8b4073bc0 completed March 14, 2026, 3:50 a.m.
Created at: March 8, 2026, 3:25 p.m.