Triple

T26336320
Position Surface form Disambiguated ID Type / Status
Subject Artyomovsky E662530 entity
Predicate locatedOnContinentBoundary P67212 FINISHED
Object Eurasia NE NERFINISHED

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: Eurasia | Statement: [Artyomovsky, locatedOnContinentBoundary, Eurasia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedOnContinentBoundary
Context triple: [Artyomovsky, locatedOnContinentBoundary, Eurasia]
  • A. liesOnBorderOf chosen
    Indicates that one entity is located along or directly adjacent to the boundary line separating it from another entity.
  • B. nearInternationalBoundary
    Indicates that one entity is located close to an international boundary separating two or more countries.
  • C. borderedByContinent
    Indicates that one entity has a land or maritime boundary directly adjacent to the specified continent.
  • D. locatedOnTerritoryOf
    Indicates that one entity is situated within or on the land area governed or owned by another entity.
  • E. connectsToCountryBorder
    Indicates that one entity is directly adjacent to and touches the border of a specified country.
  • 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_69ee81304194819092e20e0fae3aee07 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69fd67191cf88190b53ecbf5be3564e9 completed May 8, 2026, 4:31 a.m.
PD Predicate disambiguation batch_69fd654fdaac81908e67e75194710f06 completed May 8, 2026, 4:23 a.m.
Created at: April 26, 2026, 10:36 p.m.