Triple
T19622776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Register of Legislation (Australia) |
E471052
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | online legal information system |
C4395
|
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: online legal information system Context triple: [Federal Register of Legislation (Australia), instanceOf, online legal information system]
-
A.
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.
-
B.
legal database
chosen
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.
-
C.
legislative information system
A legislative information system is a digital platform that collects, manages, tracks, and provides access to legislative documents, processes, and activities to support lawmakers, staff, and the public.
-
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.
legal information category
A legal information category is a classification that organizes legal content—such as statutes, case law, regulations, or legal commentary—into distinct, searchable groupings based on subject matter, jurisdiction, or document type.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:44 p.m.