Triple
T1767924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 53 of the Constitution of Japan |
E38806
|
entity |
| Predicate | enforcedOn |
P31667
|
FINISHED |
| Object | 1947-05-03 |
—
|
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: 1947-05-03 | Statement: [Article 53 of the Constitution of Japan, enforcedOn, 1947-05-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcedOn Context triple: [Article 53 of the Constitution of Japan, enforcedOn, 1947-05-03]
-
A.
enforcedLaw
Indicates that an authority actively applies or upholds a specific law to regulate behavior or resolve situations.
-
B.
enforcedInRegion
Indicates that a rule, policy, or condition is actively applied and upheld within a specified geographic or administrative region.
-
C.
originallyEnforcedBy
Indicates that a rule, law, policy, or agreement was first implemented and upheld by a particular enforcing authority or agent.
-
D.
enforcement
Indicates the act of compelling compliance with rules, laws, or agreements through monitoring, pressure, or sanctions.
-
E.
canEnforce
Indicates that one entity has the authority or capability to compel compliance with rules, decisions, or obligations upon another entity.
- F. None of above. chosen
Provenance (4 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab39faf69c8190bae98d3e3911078f |
completed | March 6, 2026, 8:32 p.m. |
Created at: March 4, 2026, 7:31 p.m.