Triple

T32424061
Position Surface form Disambiguated ID Type / Status
Subject North Korea–Japan relations E828527 entity
Predicate publicOpinionInJapan P198016 FINISHED
Object strong concern over abductions 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: strong concern over abductions | Statement: [North Korea–Japan relations, publicOpinionInJapan, strong concern over abductions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: publicOpinionInJapan
Context triple: [North Korea–Japan relations, publicOpinionInJapan, strong concern over abductions]
  • A. ratingJapan
    Indicates that an entity assigns or holds a rating specifically related to Japan (e.g., its products, services, or overall experience).
  • B. hasPoliticalOrientationInJapan
    Indicates that an entity holds or is associated with a specific political orientation within the context of Japan.
  • C. inJapaneseCulture
    Indicates that something holds, appears, or is understood specifically within the context of Japanese culture.
  • D. givesOpinionOn
    Indicates that one entity expresses a view, judgment, or evaluation about another entity or subject.
  • E. opinionBy
    Indicates that a particular opinion, viewpoint, or judgment is expressed or held by a specific entity.
  • F. None of above. chosen

Provenance (4 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_69f3491b28bc8190b75cea7a507f337b completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fec25f0fc48190b87ab1f9cd1eb0de completed May 9, 2026, 5:13 a.m.
PD Predicate disambiguation batch_69fec079a770819098df7cc3049df954 completed May 9, 2026, 5:04 a.m.
PDg Predicate description generation batch_69fec25e3d708190be27135c57b189a5 completed May 9, 2026, 5:13 a.m.
Created at: May 1, 2026, 12:54 a.m.