Triple

T441619
Position Surface form Disambiguated ID Type / Status
Subject Quezon City E10123 entity
Predicate hasSisterCity P919 FINISHED
Object Shenyang E20553 NE 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: Shenyang | Statement: [Quezon City, hasSisterCity, Shenyang]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shenyang
Context triple: [Quezon City, hasSisterCity, Shenyang]
  • A. Shenyang chosen
    Shenyang is a major industrial and historical city in northeastern China and the capital of Liaoning Province.
  • B. Tianjin
    Tianjin is a major port city and industrial hub in northern China, located near Beijing along the Bohai Sea.
  • C. Beijing
    Beijing is the capital city of China, a major political, cultural, and economic center known for its rich history and rapid modern development.
  • D. Wuhan
    Wuhan is a major city in central China, known as a key industrial, commercial, and transportation hub located at the confluence of the Yangtze and Han rivers.
  • E. Shanghai
    Shanghai is a major global financial hub and China’s largest city, known for its modern skyline, historic waterfront, and role as a center of international business and trade.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a2e8465ef481909655c681b01e2986 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2ef42b4008190abed9d79926c7022 completed Feb. 28, 2026, 1:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69a5103417008190ab3755dbba5f7622 completed March 2, 2026, 4:21 a.m.
Created at: Feb. 28, 2026, 1:11 p.m.