Triple
T20998511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Pittsburgh School of Law |
E517214
|
entity |
| Predicate | hasPublication |
P80
|
FINISHED |
| Object | Pittsburgh Journal of Technology Law and Policy |
—
|
NE NERFINISHED |
How this triple was built (3 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: Pittsburgh Journal of Technology Law and Policy | Statement: [University of Pittsburgh School of Law, hasPublication, Pittsburgh Journal of Technology Law and Policy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pittsburgh Journal of Technology Law and Policy Context triple: [University of Pittsburgh School of Law, hasPublication, Pittsburgh Journal of Technology Law and Policy]
-
A.
Rutgers Computer and Technology Law Journal
The Rutgers Computer and Technology Law Journal is a scholarly legal periodical focusing on issues at the intersection of law, technology, and computer-related innovation.
-
B.
Stanford Technology Law Review
The Stanford Technology Law Review is an academic journal focusing on legal issues arising from technology, the internet, and intellectual property.
-
C.
Canadian Journal of Law and Technology
The Canadian Journal of Law and Technology is an academic law review focusing on the intersection of law, technology, and policy in Canada and beyond.
-
D.
Columbia Science and Technology Law Review
Columbia Science and Technology Law Review is a student-edited legal journal at Columbia Law School focusing on issues at the intersection of law, science, and technology.
-
E.
Penn Program on Regulation
The Penn Program on Regulation is a research and policy initiative at the University of Pennsylvania focused on improving the design, implementation, and understanding of regulatory systems across diverse sectors.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Pittsburgh Journal of Technology Law and Policy Target entity description: The Pittsburgh Journal of Technology Law and Policy is an academic law review focused on legal and policy issues arising from technology and innovation.
-
A.
Rutgers Computer and Technology Law Journal
The Rutgers Computer and Technology Law Journal is a scholarly legal periodical focusing on issues at the intersection of law, technology, and computer-related innovation.
-
B.
Stanford Technology Law Review
The Stanford Technology Law Review is an academic journal focusing on legal issues arising from technology, the internet, and intellectual property.
-
C.
Canadian Journal of Law and Technology
The Canadian Journal of Law and Technology is an academic law review focusing on the intersection of law, technology, and policy in Canada and beyond.
-
D.
Columbia Science and Technology Law Review
Columbia Science and Technology Law Review is a student-edited legal journal at Columbia Law School focusing on issues at the intersection of law, science, and technology.
-
E.
Penn Program on Regulation
The Penn Program on Regulation is a research and policy initiative at the University of Pennsylvania focused on improving the design, implementation, and understanding of regulatory systems across diverse sectors.
- F. None of above. chosen
Provenance (2 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc22ca6081908bf054ddcfea9e19 |
completed | April 21, 2026, 4:25 a.m. |
Created at: April 16, 2026, 1:51 p.m.