Triple
T31294355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Sex Offender Registry Board |
E798034
|
entity |
| Predicate | typeOfRegistry |
P25614
|
FINISHED |
| Object | sex offender registry |
—
|
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: sex offender registry | Statement: [Massachusetts Sex Offender Registry Board, typeOfRegistry, sex offender registry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRegistry Context triple: [Massachusetts Sex Offender Registry Board, typeOfRegistry, sex offender registry]
-
A.
registryType
chosen
Indicates the specific category or classification of a registry that an entity is associated with or recorded in.
-
B.
regulatorType
Indicates the specific kind or category of regulatory role or authority associated with an entity.
-
C.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
D.
definesRegistry
Indicates that one entity establishes or specifies a registry in which another entity is recorded or managed.
-
E.
hasRegistrationType
Indicates that an entity is associated with a specific category or type of registration it holds or requires.
- 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_69f224dfde288190af313f3c221c857e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: April 29, 2026, 9:14 p.m.