Triple
T25025092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court Act 1933 (ACT) |
E626688
|
entity |
| Predicate | typeOfCourtEstablished |
P151563
|
FINISHED |
| Object | superior court of record |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: superior court of record | Statement: [Supreme Court Act 1933 (ACT), typeOfCourtEstablished, superior court of record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCourtEstablished Context triple: [Supreme Court Act 1933 (ACT), typeOfCourtEstablished, superior court of record]
-
A.
establishedAsSeparateCourts
Indicates that one or more courts were formally created or recognized as distinct, independent judicial bodies separate from existing courts.
-
B.
originatedInCourtOf
Indicates that a legal case, decision, or proceeding began or was first filed in a specified court.
-
C.
typeOfTribunal
chosen
Indicates the specific category or kind of tribunal (e.g., court or adjudicative body) to which an entity belongs.
-
D.
createdCourt
Indicates that an entity (typically a person or organization) established or founded a particular court.
-
E.
courtName
Indicates the official name assigned to a particular court within a legal or judicial system.
- F. None of above.
Provenance (3 batches)
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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 18, 2026, 6:07 a.m.