Triple
T19129772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 郵政大臣 |
E468283
|
entity |
| Predicate | 政府レベル |
P1085
|
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.
levelOfGovernment
chosen
Indicates the specific tier or layer within a governmental hierarchy (e.g., local, regional, national) at which an entity operates or an action is taken.
-
B.
controlsLevelOfGovernment
Indicates that one entity has authority or power to direct, regulate, or determine the functioning or decisions of a specified level of government.
-
C.
governingBodyLevel
Indicates the hierarchical level or tier at which a governing body operates within a political or organizational structure.
-
D.
servesLevelOfGovernment
Indicates that one entity performs duties or functions on behalf of, or under the authority of, a specified level of government (e.g., local, regional, national).
-
E.
ownedByLevelOfGovernment
Indicates that something is owned or controlled by a specific level or tier of government (e.g., local, regional, or national).
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3cf8d348190b27fc7d7d39f46f1 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.