Triple

T5902767
Position Surface form Disambiguated ID Type / Status
Subject Spui (Amsterdam) E131266 entity
Predicate streetAddress P606 FINISHED
Object Spui E25956 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: Spui | Statement: [Spui (Amsterdam), streetAddress, Spui]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Spui
Context triple: [Spui (Amsterdam), streetAddress, Spui]
  • A. Spui chosen
    Spui is a central square and tram hub in Amsterdam, Netherlands, known for its bookstores, cultural venues, and proximity to historic canals.
  • B. Spui
    Spui is a small tidal river in South Holland, Netherlands, that branches off from the Oude Maas and plays a role in the region’s delta water system.
  • C. Bruinisse
    Bruinisse is a fishing village and tourist destination in the Dutch province of Zeeland, known for its mussel industry and location on the Grevelingen.
  • D. Spreeau
    Spreeau is a small locality within the municipality of Grünheide (Mark) in the German state of Brandenburg.
  • E. Piran Bay
    Piran Bay is a small bay in the northern Adriatic Sea, known for its picturesque coastline and the historic Slovenian town of Piran on its shore.
  • 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_69c0085864a88190a569c05ff7d65f29 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c03735e6f8819084eded3b45f5e4ed completed March 22, 2026, 6:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0b166b0bc8190a201899cf45a9b31 completed March 23, 2026, 3:20 a.m.
Created at: March 22, 2026, 3:58 p.m.