Triple

T29056145
Position Surface form Disambiguated ID Type / Status
Subject Princess of Colchis E735389 entity
Predicate locatedInLegendaryRegion P9687 FINISHED
Object eastern Black Sea 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: eastern Black Sea | Statement: [Princess of Colchis, locatedInLegendaryRegion, eastern Black Sea]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInLegendaryRegion
Context triple: [Princess of Colchis, locatedInLegendaryRegion, eastern Black Sea]
  • A. neighboringLegendaryRegion
    Indicates that one legendary region is directly adjacent to or borders another legendary region.
  • B. foundInRegion chosen
    Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
  • C. hasLegendaryPokémon
    Indicates that an entity (such as a location, trainer, or group) possesses, contains, or is associated with at least one Legendary Pokémon.
  • D. mainLegendaryPokémon
    Indicates that one Pokémon serves as the primary or central legendary Pokémon associated with a particular context, such as a game, region, or storyline.
  • E. hasPokémonLeagueLocation
    Indicates that a Pokémon League is situated at or associated with a specific geographic location.
  • 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_69f077e64b88819094d37bdbca8191b3 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69ffed8912488190baa05f572e5b1b89 completed May 10, 2026, 2:29 a.m.
PD Predicate disambiguation batch_69ffed12a76c8190ad85c6ac869c72e9 completed May 10, 2026, 2:27 a.m.
Created at: April 28, 2026, 10:11 a.m.