Triple
T30150025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebraska counties |
E766368
|
entity |
| Predicate | useCourtSystem |
P113472
|
FINISHED |
| Object | county courts of Nebraska |
—
|
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: county courts of Nebraska | Statement: [Nebraska counties, useCourtSystem, county courts of Nebraska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useCourtSystem Context triple: [Nebraska counties, useCourtSystem, county courts of Nebraska]
-
A.
usedCourt
Indicates that an entity made use of or participated in legal proceedings within a particular court.
-
B.
practiceCourt
Indicates that an entity uses or is associated with a particular court for practice or training activities.
-
C.
courtCode
Indicates the specific court or judicial body associated with a legal case, proceeding, or record.
-
D.
usedLegalSystemOf
Indicates that one entity applied, followed, or operated under the legal system or body of laws belonging to another entity.
-
E.
isPartOfCourtSystem
chosen
Indicates that one legal body, division, or component belongs to and operates within a larger court 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e8eed808190a40b139f12809e30 |
completed | May 2, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:19 p.m.