Triple
T6161315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of South Korea |
E137449
|
entity |
| Predicate | firstPromulgationYear |
P24044
|
FINISHED |
| Object | 1948 |
—
|
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 | Statement: [Constitution of South Korea, firstPromulgationYear, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPromulgationYear Context triple: [Constitution of South Korea, firstPromulgationYear, 1948]
-
A.
yearOfPromulgation
chosen
Indicates the specific year in which something, typically a law or formal decree, was officially enacted or put into effect.
-
B.
firstPromulgatedUnder
Indicates the authority, regime, or leadership under which something (typically a law, policy, or decree) was initially formally issued or enacted.
-
C.
dateOfPromulgation
Indicates the date on which a law, decree, or official act is formally proclaimed and put into effect.
-
D.
firstInscriptionYear
Indicates the year in which an entity was first inscribed, recorded, or officially entered into a relevant register or list.
-
E.
yearEnteredIntoForce
Indicates the year in which an agreement, law, treaty, or similar instrument officially became legally effective or operational.
- 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_69c008a54fc88190b6ce4416490ca79d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d35b2f88190abb9b90b5971e6d7 |
completed | March 22, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:17 p.m.