Triple
T26780709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M.G.L. |
E670237
|
entity |
| Predicate | typeOfCitation |
P32367
|
FINISHED |
| Object | statutory citation |
—
|
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: statutory citation | Statement: [M.G.L., typeOfCitation, statutory citation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCitation Context triple: [M.G.L., typeOfCitation, statutory citation]
-
A.
citationType
chosen
Indicates the specific kind or category of citation relationship that one entity has to another (e.g., reference, quotation, acknowledgment).
-
B.
typicalCitation
Indicates that one entity is commonly or characteristically cited as a reference or source for another entity.
-
C.
citationOf
Indicates that one entity cites, references, or formally acknowledges another entity as a source.
-
D.
legalCitationType
Indicates the specific kind or category of legal citation that characterizes the relationship between the citing and cited legal sources.
-
E.
hasCitationType
Indicates that a citation is associated with a specific type or category of referencing relationship (e.g., primary source, review, self-citation).
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 27, 2026, 4:08 a.m.