Triple
T5905017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 明仁 |
E131321
|
entity |
| Predicate | 憲法上の地位 |
P2259
|
FINISHED |
| Object | 日本国憲法第1条に規定される象徴天皇 |
—
|
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: 日本国憲法第1条に規定される象徴天皇 | Statement: [明仁, 憲法上の地位, 日本国憲法第1条に規定される象徴天皇]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 憲法上の地位 Context triple: [明仁, 憲法上の地位, 日本国憲法第1条に規定される象徴天皇]
-
A.
hasConstitutionalStatus
Indicates that an entity possesses a particular status, role, or recognition as defined or protected by a constitution or constitutional framework.
-
B.
constitutionalPosition
chosen
Indicates the official role, office, or status an entity holds within a constitutional or legal framework.
-
C.
constitutionalHead
Indicates that one entity serves as the official constitutional head or ceremonial leader of another entity, such as a state or organization.
-
D.
politicalPositionOnConstitution
Indicates a person's or group's stated stance, opinion, or policy position regarding a specific constitution or constitutional framework.
-
E.
isConstitutionalAuthority
Indicates that an entity holds recognized legal or institutional power derived from or defined by a constitution.
- 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0334fcf6481908e8e74105de9d49b |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:59 p.m.