Triple
T18314510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albuquerque metropolitan area |
E438719
|
entity |
| Predicate | economicHubOf |
P13740
|
FINISHED |
| Object | central New Mexico |
—
|
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: central New Mexico | Statement: [Albuquerque metropolitan area, economicHubOf, central New Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicHubOf Context triple: [Albuquerque metropolitan area, economicHubOf, central New Mexico]
-
A.
isEconomicCenter
chosen
Indicates that an entity functions as a primary hub for economic activity, such as trade, finance, or industry, within a region or system.
-
B.
regionalEconomyType
Indicates the type or classification of an economy associated with a specific region.
-
C.
isTechnologicalHubOf
Indicates that a location serves as a central focal point for technological activity, development, or innovation for another specified area or community.
-
D.
economicSectorSourceOfWealth
Indicates that a particular economic sector is the primary source from which an entity derives its wealth or income.
-
E.
regionalEconomyActivity
Indicates the type or level of economic activity occurring within a specific geographic region.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5021b7e2c81908cd3b6684ab899f6 |
completed | April 19, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.