Triple
T275575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Reports |
E5240
|
entity |
| Predicate | precedentialValue |
P3138
|
FINISHED |
| Object | binding in Massachusetts courts |
—
|
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: binding in Massachusetts courts | Statement: [Massachusetts Reports, precedentialValue, binding in Massachusetts courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedentialValue Context triple: [Massachusetts Reports, precedentialValue, binding in Massachusetts courts]
-
A.
confersPrecedenceIn
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
-
B.
precedentFor
chosen
Indicates that one situation, decision, or case serves as an authoritative example or basis for deciding or interpreting another.
-
C.
orderPrecedence
Indicates that one entity must come before another in a defined sequence or priority order.
-
D.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
E.
primaryCriterion
Indicates that one factor is designated as the main or most important basis for a decision, judgment, or selection among alternatives.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25dd1cdf881909c2c9b77b7f88684 |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b7480e881909399beccfc7ffb81 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.