Triple
T15985750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moberly, MO Micropolitan Statistical Area |
E387687
|
entity |
| Predicate | urbanCentered |
P44289
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Moberly, MO Micropolitan Statistical Area, urbanCentered, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanCentered Context triple: [Moberly, MO Micropolitan Statistical Area, urbanCentered, true]
-
A.
notableCityCenter
Indicates that a location serves as a prominent or significant central area within a city.
-
B.
urbanCenterDevelopedBy
Indicates that an urban center was created, planned, or significantly developed through the actions or initiatives of a particular agent (such as an organization, authority, or project).
-
C.
isDowntownCoreOf
Indicates that a location constitutes the central, most urbanized and commercially dense area of a larger city or metropolitan region.
-
D.
isUrbanCenter
chosen
Indicates that a place functions as a primary, densely developed hub of population, services, and activities within a region.
-
E.
connectsToUrbanCenter
Indicates that one entity has a direct or functional linkage to an urban center, such as through infrastructure, services, or regular interaction.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4e871c819082d7b1c1eaf5b4fe |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.