Triple
T13081981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooklyn Law School |
E310229
|
entity |
| Predicate | judicialProximity |
P107940
|
FINISHED |
| Object | near state and federal courts in Brooklyn |
—
|
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: near state and federal courts in Brooklyn | Statement: [Brooklyn Law School, judicialProximity, near state and federal courts in Brooklyn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judicialProximity Context triple: [Brooklyn Law School, judicialProximity, near state and federal courts in Brooklyn]
-
A.
courtBasedIn
Indicates that a particular court is located or headquartered in a specified place or jurisdiction.
-
B.
judicialCircuit
Indicates the judicial circuit within which a legal entity, case, or jurisdiction is organized or falls under authority.
-
C.
judicialFinding
Indicates a formal determination or conclusion reached by a judicial authority regarding facts, law, or liability in a legal matter.
-
D.
decisionCourt
Indicates that a particular court rendered the decision or judgment in a given legal case or proceeding.
-
E.
courtCode
Indicates the specific court or judicial body associated with a legal case, proceeding, or record.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9811add9881908a92186dab5b6d48 |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98114a6508190b1e8e018bb5a068c |
completed | April 10, 2026, 11 p.m. |
Created at: April 9, 2026, 9:01 p.m.