Triple
T18435614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makati, Michigan (historical relationship) |
E450382
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical municipal relationship |
C1073
|
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: historical municipal relationship Context triple: [Makati, Michigan (historical relationship), instanceOf, historical municipal relationship]
-
A.
historical relationship
chosen
A historical relationship is a connection between people, groups, or entities that existed in the past and is understood through documented events, interactions, and their lasting impact over time.
-
B.
municipality
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.
prefectural-level city (historical)
A prefectural-level city (historical) is an administrative division that historically combined an urban center with its surrounding rural areas under a single prefecture-level government, often serving as a regional political, economic, and cultural hub.
-
D.
municipal organization
A municipal organization is a local government entity responsible for providing public services, managing community resources, and implementing policies within a city, town, or other local jurisdiction.
-
E.
territorial relationship
A territorial relationship is a conceptual association that defines how entities claim, control, share, or interact within a specific geographic or spatial area.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:28 a.m.