Triple
T28405318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Revolutionary and Napoleonic constitutions |
E719510
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical legal document corpus |
C12841
|
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: historical legal document corpus Context triple: [French Revolutionary and Napoleonic constitutions, instanceOf, historical legal document corpus]
-
A.
historical legal text
A historical legal text is a written document from a past era that records laws, legal decisions, or legal reasoning, reflecting the legal norms, institutions, and societal values of its time.
-
B.
documentation corpus
A documentation corpus is a structured collection of written materials, such as manuals, guides, and reference texts, compiled to provide comprehensive information and support for a specific domain, product, or system.
-
C.
jurisprudence corpus
chosen
A jurisprudence corpus is a structured collection of legal texts, such as statutes, case law, and scholarly writings, compiled for analysis, research, and reference in the study and practice of law.
-
D.
historical linguistic document
A historical linguistic document is a written or recorded artifact from the past that provides evidence about the language, its usage, and its evolution in a particular historical context.
-
E.
corpus of international treaties
A corpus of international treaties is a structured collection of formal, legally binding agreements between sovereign states and/or international organizations, organized for analysis, reference, and comparative study.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:23 a.m.