Triple

T26949538
Position Surface form Disambiguated ID Type / Status
Subject Venserpolder E678741 entity
Predicate hasMetroFunction P8346 FINISHED
Object metro terminus area LITERAL 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: metro terminus area | Statement: [Venserpolder, hasMetroFunction, metro terminus area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMetroFunction
Context triple: [Venserpolder, hasMetroFunction, metro terminus area]
  • A. hasMetropolitan
    Indicates that an entity is associated with, served by, or located within a specific metropolitan area.
  • B. hasUrbanFunction chosen
    Indicates that an entity serves a specific role or purpose within an urban context, such as providing services, infrastructure, or activities typical of a city environment.
  • C. hasMetroLine
    Indicates that a location or area is served by, or connected to, a specific metro (subway) line.
  • D. isMetropolitanFor
    Indicates that one entity serves as the primary metropolitan center or urban hub for another entity (such as a region, area, or service).
  • E. hasMetropolitanConnectionWith
    Indicates that there is a significant relationship or linkage between two entities based on shared or interacting metropolitan areas, such as through infrastructure, services, or regional integration.
  • 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_69eeeb4e75f08190b14fc91ca4a91488 completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f727afd5d88190ad48735cd1b32787 completed May 3, 2026, 10:47 a.m.
PD Predicate disambiguation batch_69f72737c42c8190a3f781a5e98868ff completed May 3, 2026, 10:45 a.m.
Created at: April 27, 2026, 6:23 a.m.