Triple

T11751879
Position Surface form Disambiguated ID Type / Status
Subject MOE E279426 entity
Predicate shortName P43 FINISHED
Object MOE unclear NED1 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: MOE | Statement: [MOE, shortName, MOE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MOE
Context triple: [MOE, shortName, MOE]
  • A. MOE
    MOE is the common abbreviation for Japan’s Ministry of Education, the government body responsible for national education policy and administration.
  • B. MOE
    MOE is the Ministry of Education of the Republic of China (Taiwan), the government agency responsible for national education policy and administration.
  • C. MOE
    MOE is the government ministry responsible for overseeing and administering the national education system in South Korea.
  • D. MOE
    MOE is the elite special operations command of the Spanish Army, responsible for high-risk missions such as counterterrorism, reconnaissance, and unconventional warfare.
  • E. MoESD
    MoESD is the abbreviated name of Georgia’s Ministry of Economy and Sustainable Development, the government body responsible for economic policy, trade, and sustainable growth.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

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_69d6ab01038c819080714901502c84fc completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a509c2448190b0deb7ed29c3a73f completed April 10, 2026, 7:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69f01a13550081909a26f57b30d68e03 completed April 28, 2026, 2:23 a.m.
Created at: April 8, 2026, 9:41 p.m.