Triple

T11742290
Position Surface form Disambiguated ID Type / Status
Subject Minoru Yamasaki E279184 entity
Predicate familyName P18 FINISHED
Object Yamasaki E279184 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: Yamasaki | Statement: [Minoru Yamasaki, familyName, Yamasaki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yamasaki
Context triple: [Minoru Yamasaki, familyName, Yamasaki]
  • A. Yamasaki chosen
    Yamasaki is a Japanese surname most notably associated with architect Minoru Yamasaki, designer of the original World Trade Center in New York City.
  • B. Fumihiko
    Fumihiko is a Japanese given name most notably borne by the renowned architect Fumihiko Maki.
  • C. Tange
    Tange is a Japanese surname most famously associated with Kenzo Tange, the influential modernist architect and Pritzker Prize laureate.
  • D. Teshima
    Teshima is a small Japanese island in the Seto Inland Sea known for its contemporary art installations, scenic landscapes, and role in the Setouchi Triennale art festival.
  • E. Kuroda
    Kuroda is a Japanese surname borne by various notable figures in politics, the arts, and other fields.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6ab01038c819080714901502c84fc completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a4f191388190bd6ef7e80c41ca48 completed April 10, 2026, 7:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69f0901a6ed481909054ddd581935ac4 completed April 28, 2026, 10:46 a.m.
Created at: April 8, 2026, 9:41 p.m.