Triple
T34580818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Appeal of New South Wales |
E887895
|
entity |
| Predicate | fromCourt |
P124421
|
FINISHED |
| Object | Supreme Court of New South Wales |
—
|
NE NERFINISHED |
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: Supreme Court of New South Wales | Statement: [Court of Appeal of New South Wales, fromCourt, Supreme Court of New South Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fromCourt Context triple: [Court of Appeal of New South Wales, fromCourt, Supreme Court of New South Wales]
-
A.
hostCourtOf
Indicates that one entity serves as the venue or location where the court associated with another entity is held or convened.
-
B.
practiceCourt
Indicates that an entity uses or is associated with a particular court for practice or training activities.
-
C.
usedCourt
Indicates that an entity made use of or participated in legal proceedings within a particular court.
-
D.
destinationCourt
chosen
Indicates the court or judicial body to which a case, appeal, or legal matter is directed or transferred.
-
E.
requestedFromCourt
Indicates that a party has formally asked a court to take a specific action or provide a particular ruling or document.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720c32a60819083bd47b9b1903ebc |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:03 a.m.