Triple
T24376328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Judicial Circuit of Maryland |
E614483
|
entity |
| Predicate | isCircuitFor |
P155965
|
FINISHED |
| Object | Frederick County, Maryland |
—
|
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: Frederick County, Maryland | Statement: [Fourth Judicial Circuit of Maryland, isCircuitFor, Frederick County, Maryland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCircuitFor Context triple: [Fourth Judicial Circuit of Maryland, isCircuitFor, Frederick County, Maryland]
-
A.
hasCircuit
Indicates that an entity is equipped with, contains, or is associated with an electrical or logical circuit.
-
B.
belongsToCircuit
Indicates that something is a component or member of a specific circuit or circuit grouping.
-
C.
usesCircuitType
Indicates that one entity employs or is implemented using a specific type of circuit.
-
D.
servesCircuit
Indicates that an entity provides legal representation or service in a specified judicial circuit.
-
E.
hasCircuitRole
Indicates that an entity participates in a circuit with a specific functional role or responsibility within that 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d7fb188190bfab5e7ff83fa884 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:02 a.m.