Triple
T22440748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 皇室会議 |
E554747
|
entity |
| Predicate | 法的性格 |
P61937
|
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.
lawCharacteristicInText
chosen
Indicates that a specific legal characteristic or feature is expressed, described, or referenced within a given text.
-
B.
legalDoctrine
Indicates that one legal principle, rule, or theory is being applied, referenced, or relied upon as an authoritative basis for interpreting or deciding a legal issue.
-
C.
legalPhilosophy
Indicates the philosophical principles, theories, or viewpoints that underpin or guide a legal system, doctrine, or interpretation.
-
D.
haveCivilLaw
Indicates that an entity is subject to, governed by, or operates under a civil law legal system.
-
E.
legalSystematizationOf
Indicates the process or state in which laws, regulations, or legal principles are organized, codified, or structured into a coherent legal system or framework for something.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae1f82881908a611f134eb03f3d |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.