Triple
T36985033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagatz (High Court of Justice) |
E914937
|
entity |
| Predicate | accessToCourt |
P187246
|
FINISHED |
| Object | direct petition by individuals |
—
|
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: direct petition by individuals | Statement: [Bagatz (High Court of Justice), accessToCourt, direct petition by individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessToCourt Context triple: [Bagatz (High Court of Justice), accessToCourt, direct petition by individuals]
-
A.
practiceCourt
Indicates that an entity uses or is associated with a particular court for practice or training activities.
-
B.
courtOf
Indicates that one entity serves as the judicial body or tribunal associated with, or having jurisdiction over, another entity.
-
C.
hostCourtOf
Indicates that one entity serves as the venue or location where the court associated with another entity is held or convened.
-
D.
requestedFromCourt
Indicates that a party has formally asked a court to take a specific action or provide a particular ruling or document.
-
E.
affectedCourt
Indicates that a particular court is impacted or influenced by a specified action, decision, or legal matter.
- F. None of above. chosen
Provenance (4 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb34e4906c8190abb1c293fb84329a |
completed | May 6, 2026, 12:32 p.m. |
Created at: May 3, 2026, 4:14 p.m.