Triple
T21258587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Virginia Circuit Courts |
E523935
|
entity |
| Predicate | eachCircuitCovers |
P143414
|
FINISHED |
| Object | one or more counties |
—
|
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: one or more counties | Statement: [West Virginia Circuit Courts, eachCircuitCovers, one or more counties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eachCircuitCovers Context triple: [West Virginia Circuit Courts, eachCircuitCovers, one or more counties]
-
A.
numberOfCircuits
Indicates the total count of circuits associated with or contained in a given entity or system.
-
B.
hasCircuit
Indicates that an entity is equipped with, contains, or is associated with an electrical or logical circuit.
-
C.
usesCircuitsAlsoUsedBy
Indicates that one entity makes use of electrical circuits that are also utilized by another entity.
-
D.
minimumCircuitsRequired
Indicates the smallest number of circuits that must be present or used for a given system, configuration, or requirement to be satisfied.
-
E.
servesCircuit
Indicates that an entity provides legal representation or service in a specified judicial circuit.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e477d08190be17ad5384d69a80 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f9943ed881909ef49045c5bcf6df |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:59 p.m.