Triple

T13485606
Position Surface form Disambiguated ID Type / Status
Subject Huys te Warmond E318491 entity
Predicate locatedIn P40 FINISHED
Object Warmond E318488 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: Warmond | Statement: [Huys te Warmond, locatedIn, Warmond]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Warmond
Context triple: [Huys te Warmond, locatedIn, Warmond]
  • A. Warmond chosen
    Warmond is a village in the Dutch province of South Holland, known for its historic estates and lakeside setting popular for water sports and recreation.
  • B. Urmond
    Urmond is a village in the Dutch province of Limburg, situated along the Juliana Canal near the River Meuse.
  • C. Pelasgus
    Pelasgus is a figure in Greek mythology often regarded as an ancestral or eponymous hero of the Pelasgians, a pre-Hellenic people of ancient Greece.
  • D. Crowley
    Crowley is a surname most famously associated with Aleister Crowley, the English occultist, writer, and ceremonial magician.
  • E. Crowley
    Crowley is a suburban city located within the greater Dallas–Fort Worth metropolitan area in Texas.
  • 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_69d806b6bfec819089222715b2e86c8e completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaf3a15b48190b63fb59e926a97ae completed April 12, 2026, 2:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7463715dc8190a70a17b3ea661006 completed May 3, 2026, 12:57 p.m.
Created at: April 9, 2026, 9:42 p.m.