Triple
T19129773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 郵政大臣 |
E468283
|
entity |
| Predicate | 職務範囲 |
P22281
|
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.
workScope
chosen
Indicates the defined range, extent, and boundaries of tasks or responsibilities involved in a particular work activity or project.
-
B.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
-
C.
purposeOfWork
Indicates that one entity is the intended goal, function, or objective that motivates or justifies the work performed by another entity.
-
D.
workDescribes
Indicates that one work (such as a document, artwork, or dataset) provides a description or explanatory account of another work.
-
E.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
- 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.