Triple
T7729580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas County Courts |
E175215
|
entity |
| Predicate | typeOfCasesLimitedBy |
P31978
|
FINISHED |
| Object | statutory jurisdictional limits |
—
|
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: statutory jurisdictional limits | Statement: [Texas County Courts, typeOfCasesLimitedBy, statutory jurisdictional limits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCasesLimitedBy Context triple: [Texas County Courts, typeOfCasesLimitedBy, statutory jurisdictional limits]
-
A.
typeOfCasesHandled
chosen
Indicates the categories or kinds of cases that an entity (such as a person, organization, or system) is responsible for managing or processing.
-
B.
limitedByCourtCase
Indicates that one entity’s scope, effect, or applicability is restricted or constrained as a result of a specific court case or legal proceeding.
-
C.
jurisdictionLimit
Indicates the maximum scope or boundary within which an authority, organization, or rule is legally empowered to operate or exercise control.
-
D.
numberOfCases
Indicates the total count of individual instances, occurrences, or records associated with a particular situation, condition, or category.
-
E.
typeOfLimit
Indicates that one entity specifies the category or kind of limit that applies to another entity.
- 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_69c6995e912c81909a49a2657103f786 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7074eca4c8190bd51fd1b450729e8 |
completed | March 27, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69c7016a6cf88190b53bf4b958f0f302 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:06 p.m.