Triple
T31308296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCCA |
E798392
|
entity |
| Predicate | typeOfCourtRegulated |
P157787
|
FINISHED |
| Object | 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: court of record | Statement: [UCCA, typeOfCourtRegulated, court of record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCourtRegulated Context triple: [UCCA, typeOfCourtRegulated, court of record]
-
A.
hasTypeOfCourt
Indicates that an entity is associated with or classified by a specific type or category of court.
-
B.
typeOfJurisdiction
Indicates the specific kind or category of legal authority or control that one jurisdiction holds in relation to a given legal or administrative context.
-
C.
typeOfTribunal
Indicates the specific category or kind of tribunal (e.g., court or adjudicative body) to which an entity belongs.
-
D.
courtOf
Indicates that one entity serves as the judicial body or tribunal associated with, or having jurisdiction over, another entity.
-
E.
courtCategory
chosen
Indicates the classification or type of court associated with a legal case or judicial proceeding.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
Created at: April 29, 2026, 9:14 p.m.