Triple
T23055992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daehanminguk Heonbeop |
E574157
|
entity |
| Predicate | firstEnforcementDate |
P1124
|
FINISHED |
| Object | 1948-08-15 |
—
|
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: 1948-08-15 | Statement: [Daehanminguk Heonbeop, firstEnforcementDate, 1948-08-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEnforcementDate Context triple: [Daehanminguk Heonbeop, firstEnforcementDate, 1948-08-15]
-
A.
beganStrictEnforcement
Indicates that an entity started applying rules, laws, or standards in a much more rigorous and uncompromising manner.
-
B.
dateEnacted
Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
-
C.
dateOfEnactment
chosen
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
D.
initialEnactment
Indicates that an action, rule, or condition is being put into effect for the first time, marking its original enactment or coming into force.
-
E.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
- 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_69e245ba7ae48190be606dbc54120e39 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1867f71508190ad4513c6de2453e6 |
completed | April 29, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:55 p.m.