Triple
T38137078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | orphans' court division |
E952379
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of Pennsylvania judicial district |
C12498
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: branch of Pennsylvania judicial district Context triple: [orphans' court division, instanceOf, branch of Pennsylvania judicial district]
-
A.
judicial district
A judicial district is a defined geographic area within which a particular court or set of courts has legal authority to hear and decide cases.
-
B.
branch court
chosen
A branch court is a subsidiary judicial facility or division located away from a main courthouse to provide more accessible legal services within a specific geographic area.
-
C.
municipality in Pennsylvania
A municipality in Pennsylvania is a legally defined local government entity—such as a city, borough, township, or town—responsible for providing public services and governance within its geographic boundaries in the state of Pennsylvania.
-
D.
county of Pennsylvania
A county of Pennsylvania is an administrative and geographic subdivision of the Commonwealth of Pennsylvania that provides local government services, maintains public records, and serves as a jurisdictional unit for courts, elections, and taxation.
-
E.
federal district
A federal district is a distinct territorial unit under the direct jurisdiction of a national government, separate from any constituent state or province, typically established to house the nation's capital or serve special administrative purposes.
- F. None of above.
Provenance (1 batch)
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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.