Triple
T22891238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Integrated Electronic Litigation System |
E568044
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Singapore e-litigation platform |
C36544
|
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: Singapore e-litigation platform Context triple: [Integrated Electronic Litigation System, instanceOf, Singapore e-litigation platform]
-
A.
electronic court records system
chosen
An electronic court records system is a digital platform that securely stores, manages, and provides controlled access to court case documents, filings, and related judicial information.
-
B.
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.
-
C.
legal toolset
A legal toolset is a collection of methods, resources, and technologies designed to help individuals and organizations understand, manage, and apply legal rules and processes effectively.
-
D.
judicial network
A judicial network is a structured system of interconnected courts, judges, and legal institutions that interact through case decisions, precedents, and administrative relationships to shape and apply the law.
-
E.
legal tool
A legal tool is any instrument, process, or resource—such as contracts, statutes, case law, or software—that is used to create, interpret, enforce, or navigate legal rights and obligations.
- 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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:40 p.m.