Triple

T19845916
Position Surface form Disambiguated ID Type / Status
Subject European–Asian boundary region E476858 entity
Predicate hasDisputedDefinition P35424 FINISHED
Object true 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: true | Statement: [European–Asian boundary region, hasDisputedDefinition, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDisputedDefinition
Context triple: [European–Asian boundary region, hasDisputedDefinition, true]
  • A. hasDisputedClause
    Indicates that a particular clause within an agreement or document is subject to disagreement, challenge, or contention between involved parties.
  • B. hasDisputedStatus
    Indicates that the status or classification of something is contested, uncertain, or not universally agreed upon.
  • C. hasDisputedStatusWith
    Indicates that there is a contested or unresolved status, claim, or standing between the related entities.
  • D. disputed
    Indicates that there is active disagreement or contestation over the validity, ownership, interpretation, or status of the relationship or claim between the entities.
  • E. hasDisputedCircumscription chosen
    Indicates that there is disagreement or uncertainty about how the boundaries or scope of something are formally defined or delimited.
  • 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_69d8e51d39d081909bcfafeaaf3d2fcc completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e658091c608190b4eb9bcedd88e147 completed April 20, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69e537e21d2881909b1be82f02b99d40 completed April 19, 2026, 8:15 p.m.
Created at: April 10, 2026, 1:51 p.m.