Triple

T12993565
Position Surface form Disambiguated ID Type / Status
Subject Dagboekbrieven van 12 juni 1942 – 1 augustus 1944 E321974 entity
Predicate documentedLocation P10514 FINISHED
Object Prinsengracht 263, Amsterdam 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: Prinsengracht 263, Amsterdam | Statement: [Dagboekbrieven van 12 juni 1942 – 1 augustus 1944, documentedLocation, Prinsengracht 263, Amsterdam]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: documentedLocation
Context triple: [Dagboekbrieven van 12 juni 1942 – 1 augustus 1944, documentedLocation, Prinsengracht 263, Amsterdam]
  • A. notableLocationDocumented chosen
    Indicates that a specific location associated with an entity is recorded or documented as notable in some source or reference.
  • B. subjectLocation
    Indicates that one entity is located at, in, or near the place or position specified by another entity.
  • C. locatedIn
    Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
  • D. locationWhenGiven
    Indicates the place where an entity is located at the time it is given or transferred to another entity.
  • E. propertyLocation
    Indicates the geographical place or address where a property is situated or found.
  • 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_69d8076479b8819090afce3591939cdf completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d97f2a71a0819098bb6cf8a4b2208a completed April 10, 2026, 10:52 p.m.
PD Predicate disambiguation batch_69d97dbdd94c8190ac4bbecca02dc77b completed April 10, 2026, 10:46 p.m.
Created at: April 9, 2026, 8:44 p.m.