Triple
T13857413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Corp. v. United States |
E333100
|
entity |
| Predicate | dateArguedBeforeSupremeCourt |
P6917
|
FINISHED |
| Object | 2018-02-27 |
—
|
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: 2018-02-27 | Statement: [Microsoft Corp. v. United States, dateArguedBeforeSupremeCourt, 2018-02-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateArguedBeforeSupremeCourt Context triple: [Microsoft Corp. v. United States, dateArguedBeforeSupremeCourt, 2018-02-27]
-
A.
confirmedToSupremeCourtOn
Indicates that an individual was officially approved and appointed to serve on the Supreme Court on a specific date.
-
B.
arguedDate
chosen
Indicates the date on which an argument, debate, or legal case was formally presented or argued.
-
C.
servedOnSupremeCourtUntil
Indicates that an individual held a position on the Supreme Court up to and including a specified end date.
-
D.
openedAsSupremeCourt
Indicates that an institution or court began its operation specifically in the capacity or status of a supreme court.
-
E.
SupremeCourtVote
Indicates the voting decision or stance taken by a justice (or justices) in a case before the 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02dc9f488190b7181dcb7e304632 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.