Triple

T37396544
Position Surface form Disambiguated ID Type / Status
Subject Hamsterdam legalization experiment E928867 entity
Predicate inUniverseLocationName P120678 FINISHED
Object Hamsterdam 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: Hamsterdam | Statement: [Hamsterdam legalization experiment, inUniverseLocationName, Hamsterdam]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inUniverseLocationName
Context triple: [Hamsterdam legalization experiment, inUniverseLocationName, Hamsterdam]
  • A. inUniverseLocationType
    Indicates the type or category of location that something occupies within a fictional or defined universe or setting.
  • B. hasInUniverseLocationRelation chosen
    Indicates a relationship where an entity is associated with, or situated at, a specific location within a fictional or defined universe or setting.
  • C. inUniversePosition
    Indicates the spatial or locational position of an entity within a defined universe or world context.
  • D. inUniverseRegion
    Indicates that an entity is located within or belongs to a specific universe-defined region or area.
  • E. inUniverseProductionLocation
    Indicates the fictional location, within the narrative universe, where an in-universe production (such as a show, film, or performance) is depicted as being made.
  • 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_69f76ebb10c481909b54b9dba263e29f completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fd64bc86848190a49f451a8fc5cf1e completed May 8, 2026, 4:21 a.m.
PD Predicate disambiguation batch_69fd5ff4a648819090756d90fd195d9a completed May 8, 2026, 4 a.m.
Created at: May 3, 2026, 4:16 p.m.