Triple
T959138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court Building |
E20694
|
entity |
| Predicate | openedForUseBySupremeCourt |
P990
|
FINISHED |
| Object | October 1935 |
—
|
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: October 1935 | Statement: [Supreme Court Building, openedForUseBySupremeCourt, October 1935]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForUseBySupremeCourt Context triple: [Supreme Court Building, openedForUseBySupremeCourt, October 1935]
-
A.
supremeCourtUseFrom
Indicates that a decision, precedent, or legal principle is utilized or drawn upon by a supreme court from a particular source.
-
B.
openedForUse
chosen
Indicates that something has been made accessible and available for its intended operation or use.
-
C.
usedCourt
Indicates that an entity made use of or participated in legal proceedings within a particular court.
-
D.
SupremeCourtEffect
Indicates that an action, decision, or condition has an effect that is determined by, derived from, or constrained by the rulings or authority of a supreme court.
-
E.
hasCourtPrecedence
Indicates that one court decision or ruling holds authoritative priority over another in legal reasoning or application.
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3fc94ec8190b55c6cdf3a37d6b5 |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a18ecc8190883f6206fe3b0fb6 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.