Triple
T300200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franklin Township, Somerset County, New Jersey |
E6180
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | township in New Jersey |
C39
|
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: township in New Jersey Context triple: [Franklin Township, Somerset County, New Jersey, instanceOf, township in New Jersey]
-
A.
county in Massachusetts
A county in Massachusetts is an administrative and geographic subdivision of the state that historically provided local government functions, though many have since had their governmental powers reduced or abolished, serving primarily as regional boundaries for courts, law enforcement, and statistical purposes.
-
B.
municipality
chosen
A municipality is a local administrative unit, such as a city, town, or district, governed by elected officials and responsible for providing public services and regulations within its defined geographic area.
-
C.
census-designated place
A census-designated place is a concentration of population identified by the United States Census Bureau for statistical purposes, lacking separate municipal government but resembling an incorporated place in terms of settlement and community identity.
-
D.
former village
A former village is a once-inhabited settlement that has lost its status or population as a village, often due to abandonment, depopulation, or administrative reclassification.
-
E.
region
A region is a bounded area within a larger space, defined by shared characteristics, properties, or relationships that distinguish it from surrounding areas.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.