Triple
T18210164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. Microsoft Corp. |
E436009
|
entity |
| Predicate | initialDecisionDate |
P2232
|
FINISHED |
| Object | 2000-06-07 |
—
|
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: 2000-06-07 | Statement: [United States v. Microsoft Corp., initialDecisionDate, 2000-06-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialDecisionDate Context triple: [United States v. Microsoft Corp., initialDecisionDate, 2000-06-07]
-
A.
decisionDate
chosen
Indicates the date on which a specific decision was formally made or finalized.
-
B.
appealDate
Indicates the date on which an appeal is formally filed, recorded, or scheduled in relation to a decision or case.
-
C.
dismissalDate
Indicates the date on which an entity (such as a person, case, or employment) is formally dismissed, terminated, or ended.
-
D.
trialDate
Indicates the specific calendar date on which a legal trial or court proceeding is scheduled or took place.
-
E.
decisionEffectiveDate
Indicates the date on which a particular decision becomes valid, operative, or officially takes effect.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e228a7fc81909cfcf11cf7ce1360 |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.