Triple

T3093028
Position Surface form Disambiguated ID Type / Status
Subject Yokohama Landmark Tower E64526 entity
Predicate tallestInJapanFrom P1276 FINISHED
Object 1993 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: 1993 | Statement: [Yokohama Landmark Tower, tallestInJapanFrom, 1993]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tallestInJapanFrom
Context triple: [Yokohama Landmark Tower, tallestInJapanFrom, 1993]
  • A. isOneOfTallestIn
    Indicates that an entity is among the tallest members within a specified group, set, or location.
  • B. tallestBuildingIn
    Indicates that one entity is the tallest building located within the area or region specified by the other entity.
  • C. heldTallestStructureTitleFrom chosen
    Indicates that an entity held the title of being the tallest structure for a specified time period starting from a given point.
  • D. succeededByTallestInHongKong
    Indicates that one entity is succeeded or replaced by another entity that is the tallest in Hong Kong.
  • E. rankInCityByHeight
    Indicates the relative ordering of entities within a specific city based on their height, such as which is tallest, second tallest, and so on.
  • 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_69ad857c97d88190b26f9b1c90839c77 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada21055b88190b602425a513af7e6 completed March 8, 2026, 4:21 p.m.
PD Predicate disambiguation batch_69ad9ded78f881908be6fc0fb7c35764 completed March 8, 2026, 4:03 p.m.
Created at: March 8, 2026, 3:03 p.m.