Triple

T5405667
Position Surface form Disambiguated ID Type / Status
Subject Zolotoy Bridge E120885 entity
Predicate bayShore P13007 FINISHED
Object Zolotoy Rog Bay shoreline of Vladivostok 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: Zolotoy Rog Bay shoreline of Vladivostok | Statement: [Zolotoy Bridge, bayShore, Zolotoy Rog Bay shoreline of Vladivostok]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: bayShore
Context triple: [Zolotoy Bridge, bayShore, Zolotoy Rog Bay shoreline of Vladivostok]
  • A. bayOf
    Indicates that one location is a bay that forms an inlet or coastal indentation associated with another geographic entity, such as a sea, ocean, or coastline.
  • B. bayName
    Indicates that an entity has the specified name of a bay or is identified by that bay name.
  • C. northernShore chosen
    Indicates that one entity is located on the northern shore or northern side of another entity, typically a body of water or coastline.
  • D. bay
    Indicates that one entity howls or barks loudly, often repeatedly, typically in reaction to something such as prey, the moon, or a disturbance.
  • E. brooklynBranch
    Indicates that an entity is specifically associated with, located at, or part of the Brooklyn branch of a larger organization or system.
  • 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_69bd46391c0c81909fa484446732b6a3 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd8775e964819085c0ff5afea35f0e completed March 20, 2026, 5:44 p.m.
PD Predicate disambiguation batch_69bd8467e6b48190b9eaa9de67072e06 completed March 20, 2026, 5:31 p.m.
Created at: March 20, 2026, 2:05 p.m.