Triple
T234140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts General Laws |
E4471
|
entity |
| Predicate | codifiedFrom |
P775
|
FINISHED |
| Object | session laws of Massachusetts |
—
|
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: session laws of Massachusetts | Statement: [Massachusetts General Laws, codifiedFrom, session laws of Massachusetts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codifiedFrom Context triple: [Massachusetts General Laws, codifiedFrom, session laws of Massachusetts]
-
A.
codifiedIn
chosen
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
B.
codificationLevel
Indicates the degree or extent to which something is formally systematized, standardized, or encoded into an explicit set of rules or structures.
-
C.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
D.
compiledIn
Indicates that a piece of code, program, or module was compiled within or for a specific environment, system, or context.
-
E.
formedBy
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f14f72081908182e76300b59358 |
completed | Feb. 28, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69a25b5c8c888190b5544e687736b373 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.