Triple
T3417647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superior Court of Pennsylvania |
E72047
|
entity |
| Predicate | hasPresidentJudge |
P49339
|
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: [Superior Court of Pennsylvania, hasPresidentJudge, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPresidentJudge Context triple: [Superior Court of Pennsylvania, hasPresidentJudge, yes]
-
A.
hasChiefJudge
Indicates that an entity holds the role or position of chief judge for another entity (such as a court or judicial body).
-
B.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
-
C.
hasJudiciary
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
-
D.
hasMagistrateJudges
Indicates that one legal jurisdiction, court, or governing body includes or is served by one or more magistrate judges.
-
E.
hasPresidingOfficer
Indicates that one entity serves as the presiding officer (leader or chair) over another entity, such as an organization, meeting, or body.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb92c20fc81909b5debced20ec083 |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb23d23088190aeafe1379eae2eaa |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:15 p.m.