Triple

T12228439
Position Surface form Disambiguated ID Type / Status
Subject 香港特別行政區行政長官 E291412 entity
Predicate 政治體制角色 P72824 FINISHED
Object 行政機關首長 — 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: 行政機關首長 | Statement: [香港特別行政區行政長官, 政治體制角色, 行政機關首長]
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: 政治體制角色
Context triple: [香港特別行政區行政長官, 政治體制角色, 行政機關首長]
  • A. politicalOrSocialRole chosen
    Indicates that an entity holds or is associated with a specific political or social position, function, or status within a group or society.
  • B. partySystemRole
    Indicates the specific functional role or capacity that a party assumes within a given system or context.
  • C. roleInTaiwan
    Indicates that an entity holds or has held an official or notable role, position, or function within the political, administrative, or social context of Taiwan.
  • D. governmentalRole
    Indicates that an entity holds or is assigned a specific official position, function, or authority within a government or public administration structure.
  • E. roleInChecksAndBalances
    Indicates the part an entity plays within a system of checks and balances, such as how it constrains, oversees, or is constrained by other entities.
  • 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_69d6ab668acc8190963ba424049d6aee completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d924a3973c8190a882046963b320fb completed April 10, 2026, 4:26 p.m.
PD Predicate disambiguation batch_69d91c41bcbc81909782f4e3c571b218 completed April 10, 2026, 3:50 p.m.
Created at: April 8, 2026, 9:51 p.m.