Triple
T16475023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States circuit courts (old trial-level circuit courts) |
E400164
|
entity |
| Predicate | usedCircuitRiding |
P122922
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [United States circuit courts (old trial-level circuit courts), usedCircuitRiding, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedCircuitRiding Context triple: [United States circuit courts (old trial-level circuit courts), usedCircuitRiding, yes]
-
A.
circuitUsed
Indicates that a particular circuit is utilized or employed in performing an action, process, or function.
-
B.
usesCircuitsAlsoUsedBy
Indicates that one entity makes use of electrical circuits that are also utilized by another entity.
-
C.
usesCircuitType
Indicates that one entity employs or is implemented using a specific type of circuit.
-
D.
usedRite
Indicates that an entity performed, followed, or applied a particular rite or ritual in some context.
-
E.
performingCircuit
Indicates that an entity is carrying out or executing a specific circuit, such as a sequence of connected paths, routes, or tasks.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32dd43cf88190881a5cbc80da1490 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:13 a.m.