Triple
T9696475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middlesex Guildhall |
E234665
|
entity |
| Predicate | supremeCourtOpeningDate |
P74755
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Middlesex Guildhall, supremeCourtOpeningDate, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supremeCourtOpeningDate Context triple: [Middlesex Guildhall, supremeCourtOpeningDate, 2009]
-
A.
reopeningAsSupremeCourtDate
Indicates the date on which a case, matter, or proceeding is reopened specifically before the Supreme Court.
-
B.
hasSupremeCourtInaugurationDate
Indicates the date on which a Supreme Court justice or member was formally inaugurated or sworn into office.
-
C.
openedAsSupremeCourt
chosen
Indicates that an institution or court began its operation specifically in the capacity or status of a supreme court.
-
D.
confirmedToSupremeCourtOn
Indicates that an individual was officially approved and appointed to serve on the Supreme Court on a specific date.
-
E.
supremeCourtMandateIssuedDate
Indicates the date on which a mandate or formal order was issued by a supreme court.
- F. None of above.
Provenance (3 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d3a88788190a4235a1ab33341ec |
completed | April 1, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b9e93c8190947cce56a3925364 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:18 p.m.