Triple
T19821135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanûn-ı Esâsî |
E476195
|
entity |
| Predicate | numberOfArticlesAtPromulgation |
P137453
|
FINISHED |
| Object | 119 |
—
|
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: 119 | Statement: [Kanûn-ı Esâsî, numberOfArticlesAtPromulgation, 119]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfArticlesAtPromulgation Context triple: [Kanûn-ı Esâsî, numberOfArticlesAtPromulgation, 119]
-
A.
promulgatedAt
Indicates the time or date at which an official rule, law, or document is formally issued or put into effect.
-
B.
yearOfPromulgation
Indicates the specific year in which something, typically a law or formal decree, was officially enacted or put into effect.
-
C.
dateOfPromulgation
Indicates the date on which a law, decree, or official act is formally proclaimed and put into effect.
-
D.
firstPromulgatedUnder
Indicates the authority, regime, or leadership under which something (typically a law, policy, or decree) was initially formally issued or enacted.
-
E.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654fee3e48190ae728e49748ad268 |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:50 p.m.