Triple
T37502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Supreme Judicial Court |
E742
|
entity |
| Predicate | numberOfJustices |
P2279
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Massachusetts Supreme Judicial Court, numberOfJustices, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfJustices Context triple: [Massachusetts Supreme Judicial Court, numberOfJustices, 7]
-
A.
numberOfJudges
chosen
Indicates the total count of judges associated with a particular case, event, or entity.
-
B.
chiefJustice
Indicates that one entity serves as the chief justice (the highest-ranking judicial officer) of another entity, such as a court or jurisdiction.
-
C.
judicialBody
Indicates that an entity serves as a court or tribunal with authority to adjudicate legal disputes or interpret and apply the law.
-
D.
presidingOfficerForCount
Indicates that a particular officer has official responsibility for overseeing or presiding over a specific count (such as a charge, claim, or item) within a legal or procedural context.
-
E.
notableSupremeCourtCase
Indicates that a legal case is recognized as a significant or influential decision by 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24bb753f081909cd8b25cfb8e08af |
completed | Feb. 28, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69a24ab4a6908190b6f355415ffe7948 |
completed | Feb. 28, 2026, 1:53 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.