Triple

T9630657
Position Surface form Disambiguated ID Type / Status
Subject HafenCity development area E232793 entity
Predicate governedByPlan P44469 FINISHED
Object HafenCity master plan 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: HafenCity master plan | Statement: [HafenCity development area, governedByPlan, HafenCity master plan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governedByPlan
Context triple: [HafenCity development area, governedByPlan, HafenCity master plan]
  • A. governedFor
    Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
  • B. governedThrough
    Indicates that one entity exercises control, authority, or administration over another entity by means of a specified intermediary mechanism, structure, or process.
  • C. governancePlannedAs
    Indicates that a specific governance structure, process, or arrangement is intended or planned to be applied to an entity or context.
  • D. governed by chosen
    Indicates that an entity is under the authority, control, or administration of another entity that makes and enforces rules or decisions for it.
  • E. governedWith
    Indicates that two or more entities share or participate together in the act or process of governing.
  • 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_69ca848940cc8190b97cec654cb3bb4a completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9b01863c8190a9ec4684804f96bc completed April 1, 2026, 10:24 p.m.
PD Predicate disambiguation batch_69ccd5acfa5c8190aaba3cf548723604 completed April 1, 2026, 8:22 a.m.
Created at: March 30, 2026, 8:11 p.m.