Triple

T6997137
Position Surface form Disambiguated ID Type / Status
Subject Amsterdamse Poort E162243 entity
Predicate hasCityGateFunction P74346 FINISHED
Object former city entrance to Haarlem from Amsterdam side 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: former city entrance to Haarlem from Amsterdam side | Statement: [Amsterdamse Poort, hasCityGateFunction, former city entrance to Haarlem from Amsterdam side]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCityGateFunction
Context triple: [Amsterdamse Poort, hasCityGateFunction, former city entrance to Haarlem from Amsterdam side]
  • A. hasCityGateStatus
    Indicates the status or condition of a city gate in relation to a given entity.
  • B. hasGate
    Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
  • C. hasFaregates
    Indicates that an entity is equipped with or contains faregates used to control or validate access, typically for paid entry.
  • D. hasGatekeeper
    Indicates that one entity serves as a controlling or mediating gatekeeper for access to another entity.
  • E. hasGatesFor
    Indicates that one entity is equipped with or provides access through one or more gates intended for another entity.
  • F. None of above. chosen

Provenance (4 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_69c68857ffc08190857dc62cd5253777 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dbeef57881909245c8a5374a8111 completed March 27, 2026, 7:35 p.m.
PD Predicate disambiguation batch_69c6d7c4a18881908d267137daed828b completed March 27, 2026, 7:17 p.m.
PDg Predicate description generation batch_69c6dbbc00fc8190a18221524b774021 completed March 27, 2026, 7:34 p.m.
Created at: March 27, 2026, 2:32 p.m.