Triple
T14312557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Common Pleas of Philadelphia County |
E354868
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Pennsylvania Court of Common Pleas |
C8808
|
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: Pennsylvania Court of Common Pleas Context triple: [Court of Common Pleas of Philadelphia County, instanceOf, Pennsylvania Court of Common Pleas]
-
A.
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.
-
B.
judicial district
chosen
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.
-
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.
New York City Civil Court facility
A New York City Civil Court facility is a municipal courthouse where civil disputes involving smaller monetary claims, housing matters, and other non-criminal cases are filed, heard, and adjudicated within the NYC court system.
-
E.
Inn of Chancery
An Inn of Chancery is a medieval English legal institution that served as a preparatory training house and residence for law students affiliated with the Inns of Court.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:12 a.m.