Triple
T13415751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harris County Criminal Justice Center |
E313208
|
entity |
| Predicate | primaryCourtType |
P8214
|
FINISHED |
| Object | criminal court |
—
|
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: criminal court | Statement: [Harris County Criminal Justice Center, primaryCourtType, criminal court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCourtType Context triple: [Harris County Criminal Justice Center, primaryCourtType, criminal court]
-
A.
jurisdictionOfPrimaryCourt
Indicates the geographic or legal scope within which a primary court has the authority to hear and decide cases.
-
B.
hasTypeOfCourt
chosen
Indicates that an entity is associated with or classified by a specific type or category of court.
-
C.
trialCourt
Indicates that a legal matter, decision, or proceeding is associated with, handled by, or occurring in a court of first instance (the trial-level court).
-
D.
decisionCourt
Indicates that a particular court rendered the decision or judgment in a given legal case or proceeding.
-
E.
parentCourt
Indicates that one court is hierarchically above and has authority over another court within a 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaeb6e904819098cc9153fd2feaf5 |
completed | April 12, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:39 p.m.