Triple

T30513331
Position Surface form Disambiguated ID Type / Status
Subject Henry J. Hardenbergh (own practice) E776490 entity
Predicate notableWorkDesigner P184 FINISHED
Object The Plaza Hotel, New York City E231575 NE 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: The Plaza Hotel, New York City | Statement: [Henry J. Hardenbergh (own practice), notableWorkDesigner, The Plaza Hotel, New York City]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableWorkDesigner
Context triple: [Henry J. Hardenbergh (own practice), notableWorkDesigner, The Plaza Hotel, New York City]
  • A. namedForNotableWork
    Indicates that one entity is named in honor of another entity’s notable work or achievement.
  • B. notableWorkWith
    Indicates a relationship where two or more entities are recognized for having collaborated on or been jointly associated with a significant work or project.
  • C. designedBy chosen
    Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
  • D. architectNotedFor
    Indicates that an architect is recognized or distinguished for a particular work, style, contribution, or achievement.
  • E. notableWorkAuthor
    Indicates that one entity is the creator or author of a notable work associated with another entity.
  • F. None of above.

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_69f2249a155c8190b1d512106007e9bb completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_6a037c876524819098545e6037d3107d completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a27be6d2dcc8190910d94c0827913d2 completed June 9, 2026, 7:19 a.m.
PD Predicate disambiguation batch_6a0379e2fac0819089b522db3260028c completed May 12, 2026, 7:05 p.m.
Created at: April 29, 2026, 8:16 p.m.