Triple
T37485153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 文化勲章 |
E931510
|
entity |
| Predicate | 創設根拠法令 |
P9390
|
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.
lawEstablishedBy
Indicates that a particular law was created, enacted, or formally instituted by a specific authority, body, or individual.
-
B.
legalBasis
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
C.
establishedByStatute
chosen
Indicates that something has been formally created, defined, or authorized through a specific law or statute.
-
D.
即位の根拠法
Indicates the legal basis or law that authorizes and legitimizes a person's accession to a position of rulership or throne.
-
E.
wasPrimaryLegislationFor
Indicates that one piece of legislation served as the main or foundational legal act underpinning or authorizing another specified measure, policy, or legal instrument.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.