Triple
T7657360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BGE (Bundesgerichtsentscheide) |
E173419
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | official case law collection |
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: official case law collection Context triple: [BGE (Bundesgerichtsentscheide), instanceOf, official case law collection]
-
A.
United States Supreme Court case collection
A United States Supreme Court case collection is an organized compilation of decisions, opinions, and related materials from the U.S. Supreme Court, typically indexed and structured for legal research, reference, and historical analysis.
-
B.
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.
-
C.
legal database
A legal database is an organized digital repository that stores, indexes, and enables search and retrieval of legal materials such as statutes, case law, regulations, and secondary sources.
-
D.
law library
A law library is a specialized collection of legal resources, including statutes, case law, regulations, and secondary sources, organized to support legal research and practice.
-
E.
commercial legal research platform
A commercial legal research platform is a subscription-based digital service that provides lawyers and legal professionals with searchable access to case law, statutes, regulations, secondary sources, and analytical tools to support legal analysis and decision-making.
- 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_69c69955517c819085bc715b96d304d2 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 3:59 p.m.