Triple
T26968422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 岸田文雄内閣 |
E679236
|
entity |
| Predicate | 制度上の根拠法 |
P125
|
FINISHED |
| Object | 日本国憲法第5章 |
—
|
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: 日本国憲法第5章 | Statement: [岸田文雄内閣, 制度上の根拠法, 日本国憲法第5章]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 制度上の根拠法 Context triple: [岸田文雄内閣, 制度上の根拠法, 日本国憲法第5章]
-
A.
即位の根拠法
Indicates the legal basis or law that authorizes and legitimizes a person's accession to a position of rulership or throne.
-
B.
legalSystemBasis
Indicates the foundational legal framework, tradition, or set of principles on which a legal system is based.
-
C.
legalBasis
chosen
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
D.
governsBodyOfLaw
Indicates that one entity has authoritative control over the creation, interpretation, or enforcement of a particular body of law.
-
E.
legislatedUnder
Indicates that a law, regulation, or policy was created, enacted, or established according to the authority, framework, or provisions of a specific higher-level law or legal regime.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621233f2c81908c237f20c50c2ba3 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:37 a.m.