Triple
T7052456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court building, London |
E163998
|
entity |
| Predicate | openedAsSupremeCourt |
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: [Supreme Court building, London, openedAsSupremeCourt, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsSupremeCourt Context triple: [Supreme Court building, London, openedAsSupremeCourt, 2009]
-
A.
supremeCourtOf
Indicates that one entity serves as the highest judicial authority (supreme court) within the jurisdiction or legal system of another entity.
-
B.
supremeCourtService
Indicates that an entity serves or has served as a member (e.g., justice or judge) on a supreme court.
-
C.
succeededInSupremeCourtSeatBy
Indicates that one individual directly followed another in occupying the same seat on the Supreme 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.
supremeCourtUseFrom
Indicates that a decision, precedent, or legal principle is utilized or drawn upon by a supreme court from a particular source.
- 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_69c68861678881909961ddf4d779f750 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:37 p.m.