Triple
T25516589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Registry of Deeds (supervisory role) |
E639523
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | land records supervisory body |
C37359
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: land records supervisory body Context triple: [Massachusetts Registry of Deeds (supervisory role), instanceOf, land records supervisory body]
-
A.
land records office
chosen
A land records office is a government or municipal agency responsible for recording, maintaining, and providing access to official documents related to property ownership, boundaries, transfers, and encumbrances.
-
B.
territorial land apportionment register
A territorial land apportionment register is an official, systematically organized record that defines and catalogs the division of a country’s territory into administrative and statistical units for governance, planning, and data management purposes.
-
C.
legal record
A legal record is an official document or collection of documents that formally captures, preserves, and provides evidence of legal actions, decisions, rights, and obligations.
-
D.
land management agency
A land management agency is an organization responsible for planning, regulating, and overseeing the use, conservation, and development of public or private land resources.
-
E.
legal services regulator
A legal services regulator is an authority responsible for overseeing, licensing, and enforcing standards of conduct and competence among legal service providers to protect the public interest and maintain confidence in the legal system.
- F. None of above.
Provenance (1 batch)
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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:56 p.m.