Triple

T6604294
Position Surface form Disambiguated ID Type / Status
Subject Tokyu Plaza Omotesando Harajuku E149071 entity
Predicate secondaryLanguageSignage P16186 FINISHED
Object English 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: English | Statement: [Tokyu Plaza Omotesando Harajuku, secondaryLanguageSignage, English]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: secondaryLanguageSignage
Context triple: [Tokyu Plaza Omotesando Harajuku, secondaryLanguageSignage, English]
  • A. officialLanguageOfSignage
    Indicates that a particular language is the one officially used on public signs and signage within a given place or context.
  • B. tertiaryLanguageOfSignage chosen
    Indicates that a language is used as the third-most prominent language on signage in a given context or location.
  • C. laterSecondaryLanguageOfAdministration
    Indicates that one language served as a subsequent or later secondary language used for administrative purposes in relation to another language.
  • D. primaryLanguageSide2
    Indicates that the second entity in the relationship uses or is associated with the primary language specified.
  • E. languageOfSignage
    Indicates the language used on signs or written displays associated with an entity.
  • 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_69c687eaa7508190bb58ce2aa02039b3 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6cc9c6cb0819084fec8e0beb430de completed March 27, 2026, 6:29 p.m.
PD Predicate disambiguation batch_69c6acfd17388190bd0bb8b2371e7df1 completed March 27, 2026, 4:14 p.m.
Created at: March 27, 2026, 1:56 p.m.