Triple
T24361976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Lapeer |
E614084
|
entity |
| Predicate | isPrimaryUrbanCenterOf |
P48921
|
FINISHED |
| Object | Lapeer County |
—
|
NE NERFINISHED |
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: Lapeer County | Statement: [City of Lapeer, isPrimaryUrbanCenterOf, Lapeer County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryUrbanCenterOf Context triple: [City of Lapeer, isPrimaryUrbanCenterOf, Lapeer County]
-
A.
isMajorCenterOf
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
B.
majorUrbanCenterIn
chosen
Indicates that a city or metropolitan area functions as a primary or significant urban center within the specified region or administrative unit.
-
C.
isUrbanCenter
Indicates that a place functions as a primary, densely developed hub of population, services, and activities within a region.
-
D.
isMetropolitanCoreOf
Indicates that one area functions as the central, most urbanized core within a larger metropolitan region or system.
-
E.
capitalOrMajorCenter
Indicates that a location serves as a capital city or a primary major center (political, economic, or cultural hub) for a larger region or entity.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29384a2f88190885eb141c5c44a2d |
completed | April 29, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2 a.m.