Triple

T33016748
Position Surface form Disambiguated ID Type / Status
Subject Stadspolders E844797 entity
Predicate crossedByWaterway P27579 FINISHED
Object Wantij 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: Wantij | Statement: [Stadspolders, crossedByWaterway, Wantij]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: crossedByWaterway
Context triple: [Stadspolders, crossedByWaterway, Wantij]
  • A. waterwayTypeCrossed
    Indicates the specific kind of waterway (e.g., river, canal, stream) that is being crossed in the described relationship or action.
  • B. crossesWaterBody
    Indicates that an entity moves from one side of a water body to the other by passing over, through, or across it.
  • C. crossedByRiver
    Indicates that a river passes across or through a specified area, feature, or route.
  • D. hasCanalCrossing
    Indicates that one entity is connected to or traversed by another via a canal crossing, such as a bridge, aqueduct, or similar structure over a canal.
  • E. waterwayThrough chosen
    Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
  • 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_69f3494f3b4081909dccf2af34372a26 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f7aa699d68819081ed363931894ab3 completed May 3, 2026, 8:04 p.m.
PD Predicate disambiguation batch_69f7a8cec6d48190bebfa884b2f938c0 completed May 3, 2026, 7:58 p.m.
Created at: May 1, 2026, 1:23 a.m.