Triple
T30716234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 中共中央 |
E782029
|
entity |
| Predicate | 最高权力机关 |
P170062
|
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.
hasLegislativePower
Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
-
B.
行政権の所在
Indicates the relationship specifying where (in which body or institution) the authority to exercise executive power is vested.
-
C.
ultimateExecutiveAuthority
Indicates that one entity holds the highest-level decision-making and governing power over another entity or domain, with no higher authority above it in that context.
-
D.
legislativePowerScope
Indicates the range or extent of authority that a legislative body has to create, amend, or repeal laws.
-
E.
hasLegislativeHead
Indicates that an entity (such as a government or legislative body) has a specific person or office serving as its legislative leader or head.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c5343b8819082ded39e2e8ee1c8 |
completed | May 2, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:35 p.m.