Triple
T19821095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanûn-ı Esâsî |
E476195
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman legal document |
C27413
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Ottoman legal document Context triple: [Kanûn-ı Esâsî, instanceOf, Ottoman legal document]
-
A.
Ottoman law
Ottoman law refers to the complex legal system of the Ottoman Empire, combining Islamic (Sharia) principles, sultanic decrees (Kanun), and customary practices to govern its diverse populations and administrative affairs.
-
B.
Mughal-era legal code
A Mughal-era legal code is a structured body of laws, regulations, and judicial principles developed under the Mughal Empire that governed civil, criminal, fiscal, and religious matters by blending Islamic jurisprudence with local customs and imperial decrees.
-
C.
historical political document
chosen
A historical political document is an official or influential written record produced in a past political context that reflects, shapes, or codifies governmental decisions, ideologies, or power relations of its time.
-
D.
Ottoman order
An Ottoman order is a formal honor or decoration bestowed by the Ottoman Empire to recognize distinguished service, loyalty, or achievement in military, civil, or diplomatic fields.
-
E.
Polish historical document
A Polish historical document is an original or reproduced written, printed, or otherwise recorded source created in or about Poland’s past, providing evidence and context for historical events, people, institutions, or cultural practices.
- F. None of above.
Provenance (1 batch)
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. |
Created at: April 10, 2026, 1:50 p.m.